Contract Parsing MCP for the AI you already use
Check credits, validate a batch, create secure uploads, start parsing jobs, and retrieve structured results through one governed MCP connection.
A parser workflow the AI can follow
Each step is explicit, inspectable, and backed by the same Parsing Platform controls.
Know the cost before you queue
Check available credits and preflight the proposed batch before creating paid work.
“Check our parser credits and preflight a 12-file extraction batch before you queue anything.”
Upload through a secure handoff
Create short-lived upload URLs for the files your client can transfer, without putting file bytes inside MCP tool arguments.
“Create upload URLs for these three agreements and tell me which files still need to be transferred.”
Track jobs to structured results
Create a parsing job, inspect its status, and retrieve the completed extraction from the conversation.
“Start the approved batch, then list the jobs and summarize completed versus failed files.”
Upload and parsing are separate steps
That separation keeps large files out of chat arguments and avoids implying support a client does not have.
- 01
Preflight the batch
Validate file counts and credit requirements before any parser job is admitted.
- 02
Transfer supported files
Claude, ChatGPT or Codex uploads the bytes to Contracko's short-lived URL. If it cannot, upload in the Contracko app and continue there.
- 03
Queue and retrieve
Create the job only after upload, then poll its status and retrieve the structured output when ready.
Connect Contracko MCP to Claude, ChatGPT, Codex or your CLI
Pick your assistant for setup steps that match its current MCP support, from a two-click connector to a single command in the terminal.
Contracko MCP endpoint
Install prompt
Claude
Add Contracko from Claude's connector directory with one click. It works on web, desktop, mobile and Cowork, on every Claude plan including Free. On Team and Enterprise, an Owner enables it first. On Pro and above you can also install the Contracko plugin (Customize, Plugins) for the four contract skills, then connect from its Connectors tab.
-
Choose Connect to Claude, sign in to Contracko and pick your workspace. Claude Code signed in with the same Claude account picks the connector up too.
-
Added Contracko as a custom connector before? Remove that one, or you will see every tool twice.
ChatGPT / Codex
ChatGPT connects to MCP servers as apps. On Business and Enterprise you create one in developer mode, and an admin can publish it to the whole workspace. Pro developer mode is read-only.
-
Open Settings → Security and login and turn on Developer mode.
-
Add an app with the Contracko endpoint and sign in with OAuth. Optionally, an admin can publish it to the whole workspace under Workspace settings → Apps.
Cursor
Cursor installs a custom MCP server straight from a link, so there is no configuration file to edit. Click the button, confirm the server in Cursor, and sign in with your Contracko account.
-
Click Add to Cursor. Cursor opens and asks you to confirm the contracko server and its endpoint.
-
Sign in with OAuth and pick a workspace. The Contracko tools then appear in Cursor's MCP list. The first command below is the setup prompt; the second adds the skills library.
CLI, VS Code and coding agents
Claude Code, Codex CLI, Warp, Kilo Code, Qwen Code and Antigravity each read custom MCP servers from their own configuration, so there is no admin to wait for. The Claude Code command installs the Contracko plugin, which registers the server and brings the skills, so you do not add the server separately. VS Code adds the same server from the Add to VS Code button. This is also the only way to reach Contracko from Gemini, since the Gemini app cannot use custom MCP servers.
-
Pick your coding agent, copy its command, and sign in with OAuth. VS Code uses the Add to VS Code button instead.
-
Install the skills library so the agent knows how to import a contract pile, review renewals and file new agreements rather than guessing.
Microsoft 365 Copilot
Admin-enabledMicrosoft 365 Copilot only reaches external tools through federated connectors: read-only, published by the vendor, and switched on by your Microsoft 365 admin. Contracko write workflows are not a direct install in Copilot Chat.
-
Ask your Microsoft 365 admin to enable the read-only Contracko connector once it is listed in the Connectors Gallery.
-
Then connect it yourself in Copilot Chat → Settings → Sources and sign in to Contracko.
You stay in control, whichever assistant you use.
Claude, ChatGPT or your own coding agent reads only what your account can reach, and nothing is written, changed or deleted without your approval. That makes it safer than a standing API key, and it lets you keep the assistant that already understands your work.
You are in the driver's seat
The assistant acts as you, inside the workspace you picked, and never gets its own account. Anything you cannot open in Contracko, Claude or ChatGPT cannot open either.
Read and write are separate
You approve read or write access at connection time, and write-capable actions go through your client's approval step before they run.
Every action is visible
Created and updated records carry normal validation and land in activity history, labelled as coming from MCP.
Parser MCP questions
Credits, uploads, job admission, and client compatibility explained plainly.
Put contract extraction inside your AI workflow
Connect the Parser MCP, validate the batch first, and keep paid queue admission explicit.
AI agent reading this? The whole page is also available as Markdown