The DraftPilot MCP server is DraftPilot’s public API for AI agents. It lets an assistant such as Claude or ChatGPT find, search and read the contract playbooks your DraftPilot account can access, so the assistant can answer questions using your organization’s approved negotiation positions.
It is a hosted service. There is no package, SDK or CLI to install: you add a URL to your MCP client and sign in with your normal DraftPilot account.
Availability
The MCP server is in pilot. Your organization must have it enabled before anyone can connect. To join the pilot, email [email protected]. To try DraftPilot itself, request a demo.
Connection URL
Signed-in users find their exact URL in the DraftPilot web app under Profile → MCP connections. Always use the URL shown there.
| Region | MCP endpoint |
|---|---|
| EU | https://api.draftpilot.ai/mcp |
| US | Shown in the US web app |
EU and US are separate deployments. Connect to the region your organization’s account lives in.
Transport
- Streamable HTTP, stateless, JSON responses (
POST /mcp) - MCP protocol versions 2025-11-25, 2025-06-18 and 2025-03-26
- No server-initiated notifications
Authentication
The server uses OAuth 2.1. There are no API keys and no client secrets.
- Discovery: an unauthenticated request returns
401with aWWW-Authenticateheader naming the protected resource metadata URL - Client registration: dynamic client registration (RFC 7591) for public clients with HTTPS redirect URIs
- Grant: authorization code with PKCE (
S256), plus refresh tokens - Consent: each person signs in and approves the connection for their own account, including any SSO their organization requires
Access tokens last 15 minutes. Refresh tokens last 90 days and rotate on every use. A user can revoke a connection at any time from MCP connections in DraftPilot.
Machine-readable metadata
- Protected resource metadata (RFC 9728): https://api.draftpilot.ai/.well-known/oauth-protected-resource/mcp
- Authorization server metadata (RFC 8414): https://api.draftpilot.ai/.well-known/oauth-authorization-server
- API catalog (RFC 9727): https://draftpilot.ai/.well-known/api-catalog
Scopes
Request only the scopes your agent needs. If no scope is requested, the server grants playbooks:read.
| Scope | Grants |
|---|---|
playbooks:read | Find, search and read the playbooks the signed-in user can access |
usage:read | Read DraftPilot usage statistics, for users allowed to view usage |
contracting:write | Create and progress contracting requests on the user’s behalf |
A scope never widens a user’s access. Every call is also limited by the user’s DraftPilot workspace permissions, including accepted guest workspaces in other organizations. The metadata above is the authoritative list of supported scopes.
Tools
With playbooks:read, the server exposes these read-only tools:
| Tool | What it does |
|---|---|
list_playbooks | Lists the playbooks the user can access, with their workspaces |
search_playbook_entries | Searches playbook guidance and returns matching excerpts |
get_playbook | Reads a complete playbook’s guidance, in order |
Results are paged. Keep calling with next_cursor until complete is true. Search results can be excerpts, so read the whole playbook with get_playbook before relying on its full guidance.
When to use it
Use the DraftPilot MCP server when an agent needs an organization’s own contract positions, for example to:
- Check what a team’s playbook says about a clause, such as a liability cap, indemnity or governing law
- Quote the preferred position, fallbacks and escalation rules for a contract type
- Compare a counterparty’s proposed wording against the approved playbook guidance
- List which playbooks and workspaces a user can draw on
Do not use it to redline a Word document. DraftPilot’s reviews and tracked-change redlines run inside the Microsoft Word add-in, not over MCP.
Example prompts
- “Use DraftPilot to list the playbooks I can access. Include their workspaces.”
- “Use DraftPilot to find guidance about liability caps. Identify the source playbook for each result.”
- “Read the complete NDA playbook from DraftPilot and summarize its fallback positions.”