Juro contracts

Name: Juro contracts MCP Server
Availability: InStock
Author: Juro contracts

HIPAA CompliantSOC2 ReadyISO 27001 Ready

Productivity5 tools

Search a contract repository in natural language, download a contract and push a revised file back as a new version, from Claude or ChatGPT. Five tools listed by Anthropic, OAuth sign-in, activated by a Juro Org Admin.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 8 September 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Juro contracts via MCP

https://integrations.app.juro.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Use in Agentman

Connect Juro contracts once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Juro contracts Tools & Capabilities (5)

download-document

fetch

graphql-search

request-upload-url

upload-document-version

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The tool list is Anthropic's, not the server's. The endpoint returned HTTP 401 to our anonymous initialize on 2026-09-08, so we read no tool descriptions, no input schemas and no safety annotations. Treat the five names as a listing, and treat the read/write column above as inference.
graphql-search has no published schema. What the GraphQL interface can query is undocumented, so its reach cannot be sized from public material. This is the connector's largest unknown.
fetch is undocumented. Juro names it nowhere we could find; what it returns is not public.
Smartfield updates are not supported. Juro states this in its own capability table for both Claude and ChatGPT — edits reach the document body only.
Uploads are blocked on signed contracts. Juro documents versions as uploadable onto unsigned contracts only, with a further carve-out for contracts sent through its asynchronous negotiation flow.
A large diff stops being a diff. Above 200 individual suggestions, Juro replaces the contract with the uploaded version rather than itemising the changes.
Some Word edits never appear as redlines. Juro lists formatting-only tracked changes, edits in headers and footers, table styling and image changes as not importable as suggestions — so a reviewer approving a redline set has not necessarily seen everything that changed.
No version management from the agent. Restoring, comparing and renaming versions are Juro UI actions; no listed tool performs them.
Capability differs by client. Juro documents seven actions for Claude, five for ChatGPT and two for Wordsmith. Dashboards and the Slack/Word add-in route are listed for Claude only.
Activation is not self-serve. A Juro Org Admin must enable MCP, and in Claude a second Owner-level change is required before editing, downloading or uploading works at all.
Juro publishes an explicit AI accuracy warning. Its guidance states AI output is probabilistic, that AI "can't tell you when it's uncertain", that it handles unusual inputs less reliably, and that output "must be checked before you rely on it". Juro's Operator article repeats it: always review responses before relying on them.
Rate limits for the MCP endpoint are not published. Juro documents rate limits for its REST API v3 — 10 requests per second, and a monthly quota of 100 requests without an API subscription against 20,000 per day with one — but does not state whether the MCP server shares them. Do not assume it does.
This is contract data. The connector reads and writes documents of record. Nothing on this page is legal advice, and Agentman does not endorse Juro or assess its service.

Frequently asked questions

You need a Juro account and, for Claude, a Pro, Max, Team or Enterprise plan — Juro names those four Claude tiers in its own setup article. Juro does not publish a separate MCP add-on price or a minimum Juro subscription tier for the connector, so confirm what your Juro contract covers with your Customer Success Manager before you plan around it.

A Juro Org Admin. Juro documents one shared activation step ahead of every client: an Org Admin opens Connectors, chooses MCP, clicks Connect and copies the server URL that appears. No other role can do it, so an individual user cannot self-serve the connector. Editing, downloading and uploading in Claude need a second step from a Claude Owner.

No. Juro states the connector respects your Juro permissions, so you only see and query what you already reach in the app. Juro's access model is group-based: a document you lack access to is invisible in your environment, returns nothing in search results, and errors on a direct link. The connector inherits that boundary rather than adding one.

It depends on how the contract was created, and Juro documents both paths. A contract built from a Juro template keeps its identity: Juro compares the uploaded file against the current version and shows the differences as reviewable redlines. A contract that originated as an uploaded Word file works differently — there a new version simply replaces the previous one.

Yes, but in the Juro app rather than through the connector. Juro documents a restore flow: open the document timeline, go to the Versions tab, view the version you want, click Restore this version and name the restored version. None of the five tools Anthropic lists for this connector restores, compares or deletes a version, so recovery is a human step in Juro's UI.

No. Juro states that versions can be uploaded onto unsigned contracts only, and that a signature added in Juro must be removed through its Unsign and edit flow first. Juro adds a second carve-out: where a contract has gone through its asynchronous negotiation flow, a version cannot be uploaded and marked as fully signed.

Juro states that its MCP configuration is set to opt out of model training, in a September 2025 post by CEO Richard Mabey. That post also tells customers to configure their own AI tenant settings to prevent training, describing the pair as belt and braces. The vendor's position covers Juro's side of the connection, not your AI client's defaults.