AI Integrations (MCP & API)

Your team already works in AI clients like Claude, Cursor, and Claude Code. Without a connection to Pactly, answering “what does our latest MSA with this counterparty say?” means leaving the assistant, searching the repository by hand, and pasting clause text back in.

Pactly’s MCP server closes that gap. It exposes your contract data to any MCP-compatible client as a set of read-only, company-scoped tools, so the assistant can search contracts, read clause text, and look up playbooks on your behalf, all authenticated against your workspace.

The Model Context Protocol (MCP) is an open standard for connecting AI applications to external tools and data. Instead of copying information between Pactly and your assistant, MCP gives the assistant a direct, structured channel to call Pactly tools and read the results.

Pactly runs an MCP server at a single endpoint. You configure your AI client to connect to it, authenticate with your workspace credentials, and the client’s model decides which tools to call to answer your prompts.

The server exposes eight tools across four areas. Each one only reads; none create, modify, or delete anything in Pactly.

• Search contracts by status, category, owner, party, date range, or keyword
• Read contract text to summarize, compare, or analyze clause language
• Look up contract details including parties, approval history, and properties
• Find parties to see who your company works with
• Browse playbooks and their positions, keywords, and fallback clauses
• Search the clause library for standard language by title or tag

Once connected, you can ask your assistant things like:

• “Find all NDAs that are pending signature.”
• “Get the full text of contract 2026-0040 and summarize its termination clause.”
• “What parties do we work with, and how many contracts do we have with each?”
• “Show me the positions in our NDA playbook.”
• “Find clauses related to indemnity in our library.”

For the full parameter, response, and status-code detail on each tool, see the MCP Tools Reference.

The server accepts two credential types. Both are scoped to your company and grant read-only access.

The simplest path. Generate a key from Account Settings → API Keys → Create New API Key, then add it to your client config as an x-api-key header. The key is shown once at creation, so copy it immediately. See MCP Setup for per-client configuration.

For clients that connect over OAuth (such as remote MCP connectors), Pactly supports the full OAuth 2.1 flow: authorization code with PKCE and dynamic client registration. Granting consent requires an admin or master role on the workspace, so a non-admin user cannot authorize a new client on their own.

• Read-only. MCP tools read contract data; they cannot create, modify, or delete anything.
• Company-scoped. A connection only reaches data belonging to your company.
• Authenticated per request. Every call carries your API key or OAuth token.
• Rate-limited. Requests are throttled per API key to protect the workspace.
• Stateless. Each request uses a fresh transport, with no session state carried between calls.

• AI Assist (in-app): Pactly’s conversational AI inside the web app and Word add-in
• MCP Tools Reference
• Admin settings