Claude Juro contracts connectorWhat Claude can do in your Juro contracts account.
The Claude Juro contracts connector exposes 7 tools. 2 of them read your contract library, 3 change something in it, and 2 are documented nowhere. Below: what Claude finds, what it can draft, what your admins must switch on, and where sources clash.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach your contracts
Instead of opening Juro, filtering the repository and scrolling through a document to find one clause, you ask Claude in plain words and it goes looking itself. It searches the text of your contracts and their smartfields, the structured values Juro keeps on each document, and brings the answer back into the conversation.
Find the right agreement fast. A sales lead asks for the latest NDA signed with a given customer: Claude runs graphql-search across contract bodies and smartfields, then points you to the match.
Start a contract from what legal approved. With create-contract, Claude opens a new agreement from one of your team's approved templates, nothing else. Juro describes no way to start from a blank page or from an outside file.
Keep the record current. After a negotiation, update-smartfields sets new values on a document, and upload-document-version pushes a revised file back as a fresh version of the same contract record rather than a separate one.
Now the part the directory does not tell you. Downloading, uploading and editing only work once an owner of your Claude organization has turned on code execution, network access and Juro's domain. Claude sees only what your own Juro permissions already show you. And nothing runs by itself: no tool wakes up when a contract is signed or expires. If you need that kind of hands-off flow, it belongs to an automation tool, which does a different job; the Integrations hub covers that side.
Five words before you connect
The vocabulary Claude uses around this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the tools it needs on its own, and the directory lists them by name.
- Authorization
- The sign-in screen of the service itself, where you grant the access Claude will use. Given once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Juro.
Connect Juro to Claude in three steps
- 01
Find Juro in Claude
Open Claude's settings, go to Customize then Connectors, and look up Juro in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can each sign in.
- 02
Start the connection
Click Connect on its row, then log in to Juro in the window that Juro opens itself. If the link ever breaks, Disconnect and connect again. The window belongs to Juro, not to Claude.
- 03
Read the authorization screen
Check the authorization screen before you accept it. That screen belongs to the service, not to Claude, and it is what sets what the access covers. Access granted there can also be withdrawn later from the Juro account itself.
The 7 tools, split by what they do
Juro contracts gives Claude 7 tools: 2 that read your account, 3 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. Tool names stay exactly as Claude shows them.
- 2 read
- 3 write
- 2 not documented
What Claude reads (2)
2 toolsTwo tools that look at your contracts and leave them as they are.
download-document
Pulls a contract out of Juro so you can keep working on it offline or hand it to another app. You get the file itself, not a summary of it.
graphql-search
Looks through your repository in plain language, reading both the body text of each contract and its smartfields. Claude gets back the matching documents and can dig into them from there.
What Claude changes (3)
3 toolsThree tools that alter your Juro account. No source spells out their confirmation, so the general rule below applies.
create-contract
Approval: see the ruleOpens a brand new contract in Juro, built from one of the templates your team has approved. Claude cannot invent the structure: the template sets it.
update-smartfields
Approval: see the ruleSets new values on the smartfields of an existing document, the structured data Juro tracks such as a party name or a date. The contract record stays the same; its fields are refreshed.
upload-document-version
Approval: see the rulePushes a revised file back into Juro and files it as a new version of the contract it came from, so the history stays in one record instead of two.
Undocumented (2)
2 toolsThe directory publishes these two names and nothing more. No official text says what they do, and we will not guess it from a name.
fetch
This name sits in the directory's tool list and that is all we know. Juro's help article does not mention it, nor does any Claude page, so this page says nothing more about it.
request-upload-url
Same silence here: the name is listed, no official source describes it. We would rather flag the gap than fill it with a guess drawn from how the name sounds.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. The prompt appears in the conversation when it matters.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do across the whole organization, for instance keeping reading on and writing off. That choice binds everyone, and nobody overrides it from a personal account. Claude also works with the rights of the person who connected and nothing beyond: a contract you cannot open in Juro stays out of its reach too.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, and that is a real hole in the catalog.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. Juro's own article says something narrower; the limits section below sets both side by side. To check the live state, the connector's sheet in the official directory is the place to look.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when a contract is signed, renewed or about to lapse.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The partner badge in the directory is not a security audit either, and Anthropic states on every sheet that it neither chooses the tools a publisher exposes nor guarantees they behave as announced. Connect only what comes from a publisher you trust, here Juro itself. For a connector whose sources openly contradict each other on what it can send, see the Claude gmail connector page.
Which Claude plans can use this connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise an Owner has to enable each one first.
- Publisher's help article ↗September 2026The publisher lists Pro, Max, Team or Enterprise as the plans needed.
What this page followsNeither is outdated: Anthropic's rule covers every connector, while the publisher's line targets this one alone and is therefore the more specific. It is the publisher speaking, not Anthropic, so check the directory sheet on your own account before relying on either.
Need help connecting Juro contracts to Claude?
A person reads every message.
