6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search a contract repository in natural language, download a contract and push a revised file back as a new version.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Juro MCP server connects a Juro contract repository to Claude, ChatGPT and Wordsmith. Search contracts in plain language, pull key terms out of an agreement, download a document, and push a revised file back as a new version of the same contract record. Sign-in is OAuth, and a Juro Org Admin must switch the connection on first.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.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.
…/15956673-claude-mcp, which is a 301 to this article — the article ID changed and the slug was retitled from claude-mcp to juro-mcp as the article grew to cover three clients. We cite the resolved URL. · retrieved 2026-09-08x-api-key auth. Contains no occurrence of "GraphQL" — the basis for the undocumented-schema finding) · retrieved 2026-09-08www-authenticate: Bearer resource_metadata="…/mcp/.well-known/oauth-protected-resource", scope="juro:mcp:read juro:mcp:write". A GET on the same path returns the identical challenge; the bare host returns 404 · retrieved 2026-09-08resource_documentation, which names the help-centre root rather than the MCP article) · retrieved 2026-09-08https://oauth.app.juro.com, and the same two juro:mcp:* scopes alongside offline_access, offline and openid) · retrieved 2026-09-08totally-fake-xyz-999 straight back in its resource field, so a 200 there is evidence about the URL shape and not about what exists. The path-suffixed form named in the www-authenticate header does discriminate — the same invented name returns 404 — so only that form is cited above as evidence about this resource. · retrieved 2026-09-08intercom.help/robots.txt (fetched 2026-09-08) disallows three error and template routes, sets a crawl-delay, and carries no Content-Signal line on any axis — no ai-input preference is expressed. intercom.help/juro/llms.txt (98 lines) and intercom.help/juro/sitemap.xml (85 URLs) both resolve, and appending .md to any article URL returns clean Markdown; every help-centre citation above came through that route · retrieved 2026-09-08Connect Juro contracts once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.