Ivo MCP Server

Last updated: September 1, 2026

Ivo supports the Model Context Protocol (MCP), the open standard for connecting AI tools to your data. Connect Claude, Cursor, or any MCP-compatible client to your Ivo workspace and query your contract repository in plain language with answers grounded in your actual agreements, amendments, and extracted terms.

1   Security and Access

Control

How it works

Authenticated as you

Every connection authenticates as a specific user through your existing Ivo sign-in (including SSO) or a revocable workspace API key.

Your permissions apply

Each user sees only the Rooms they already have access to: the same room-level permissions that apply inside Ivo apply over MCP.

Auditable

Key activity is captured in your workspace audit log.

Single-tenant

Everything runs inside your dedicated Ivo environment.

2  Getting Connected

Your workspace’s MCP server URL is available in Ivo under Settings > MCP, with one-click copy and API key management. We recommend setting up the connection through Claude in your web browser; once configured, it’s also available in the Claude desktop app.

AVAILABILITY

MCP access is part of Ivo’s repository (Intelligence) offering. Contact your Ivo team if you don’t see the Settings > MCP tab and would like it enabled

3  How It Works

The server exposes three tools that together form a conversational loop:

Tool

What it does

GetRooms

Lists the Rooms you can access, pre-filtered by your Ivo permissions, so you (or your AI client) can choose which Room to query.

QueryRepository

Takes a natural-language question: optionally scoped to a Room and optionally continuing a prior conversation: and starts a full assistant run. It returns immediately with a reference while the work runs in the background.

PollPromise

Checks on a running query. While the query is in flight it streams Ivo’s latest activity as progress updates; when finished it returns the answer, any result tables, a report summary, and a conversation ID for follow-up questions.

Conversations are stateful. Passing the conversation ID into your next question continues the same chat with full context, so multi-turn analysis works the way it does inside the Ivo app. Queries over MCP run with repository search and web search enabled, and these conversations are kept separate from your normal chat history in Ivo.

4  Two Ways to Authenticate

>  OAuth sign-in

The server implements the modern MCP authorization stack: OAuth 2.1 with mandatory PKCE, dynamic client registration, and standards-based protected-resource discovery. Add your workspace URL to Claude or Cursor, sign in through Ivo’s standard login (including SSO), and your client receives tokens automatically (no manual credential handling). Hosted Claude connectors work out of the box.

  • Access tokens last 2 hours by default; refresh tokens last around 6 months and are single-use with automatic rotation.

  • If a user’s credentials change, all of their outstanding tokens are revoked automatically.

  • OAuth sign-in operates at the individual user level. For system- or service-account connections, use a workspace API key.

> Workspace API keys

From Settings > MCP, users can generate named API keys with expiries of 30 days, 90 days, 1 year, or 30 years. Keys use the standard Authorization: Bearer <token> header.

  • Each key is shown once at creation: Ivo stores only a hash of the secret, so a key can never be recovered afterward.

  • Members manage their own keys; workspace Admins can view and revoke every key in the workspace.

  • Key creation and deletion are recorded in the workspace audit log.



5  What to Expect

Area

Details

Repository Q&A, read-only

MCP access is for asking questions of your repository. Document upload, playbook review, drafting, and editing continue to happen in the Ivo app, and Ivo’s deep research mode is not available over MCP. If you need to export data (for example, extracted fields into a data warehouse), Ivo’s public API is the right tool.

Answers stream as Ivo works

Real repository questions take time to answer well. Progress updates stream while Ivo works: the same “thinking” experience as the Ivo app. Clients like Claude handle this seamlessly; simpler clients may surface the underlying polling.

Interactive and light automated use

Concurrency is capped at 2 simultaneous queries per key and 6 per workspace; automation that fans out many parallel questions should serialize its requests.

Large result sets are paged

Returned tables show a page of rows with a “Showing X of Y results” footer; very large result sets aren’t fully inlined into the response.

READY TO CONNECT?

Find your MCP server URL under Settings > MCP, or contact your Ivo team to enable access for your workspace.