---
title: "Import and organize contracts with AI (MCP)"
description: "Extract contract data with an MCP server: hand a pile of agreements to Claude or ChatGPT and get each one filed with parties, dates and values captured."
canonical: "https://contracko.com/blog/extract-contract-data-with-mcp"
---
# Import and organize contracts with AI (MCP)

Source: https://contracko.com/blog/extract-contract-data-with-mcp

[Blog](https://contracko.com/blog)

[Import and organize contracts with AI (MCP)](https://contracko.com/blog/extract-contract-data-with-mcp)

# Import and organize contracts with AI (MCP)

Budi Voogt Sep 13, 2026

Copy for LLM

Drop a pile of agreements into the AI assistant you already use and get each one filed under the right counterparty, with parties, dates and values captured, without typing a field. That is what it means to extract contract data with an MCP server: the assistant hands the documents to Contracko, Contracko reads the details out of them, and you approve the result.

## What importing a pile looks like

MCP, the Model Context Protocol, is the open standard that lets an assistant work with a product's real records rather than what you paste into a chat window. For the longer version, start with [what a contract management MCP server is](https://contracko.com/blog/what-is-a-contract-management-mcp-server). The exchange below is an illustrative example with fictional counterparties, not recorded product output.

> Import every agreement attached here and file each under the right counterparty.

| Counterparty | Agreements | Filed as |
| --- | --- | --- |
| Harbour Foods BV | 3 | Existing counterparty |
| Larkspur Systems | 2 | New counterparty |
| Vellum Print Co | 1 | New counterparty |
| 6 other counterparties | 6 | 4 existing, 2 new |

Two files had no signature page, so the assistant flagged those instead of guessing. It then offered to set reminders for the notice dates it found.

## What gets captured and filed

The import is where contract data stops being locked in a PDF. [Contracko's extraction](https://contracko.com/docs/contract-data-extraction) reads the agreement and fills the record, no template required, so a supplier agreement arrives with:

Identity and parties

- Contract title and type, which decides the fields the record carries
- Parties and their roles, matched to an existing counterparty when there is one, so a third agreement with the same supplier lands under that supplier rather than beside it

Dates and deadlines

- Effective date, start date and end date, kept apart because signing, taking effect and the current term are three different things
- Renewal terms and notice periods, which Contracko keeps as [separate inputs from the end date](https://contracko.com/docs/contract-dates), so an auto-renewal and its notice deadline are recorded rather than inferred

Financial terms

- Fees, billing frequency and currency, so a monthly fee stays monthly and an amount keeps the currency it was written in
- License counts, service tiers or project codes, where you have [custom fields](https://contracko.com/docs/custom-fields) configured on the contract type for text, dates, currency or a set list

Risk and obligations

- Liability caps and exclusivity clauses, extracted as terms rather than left in the prose
- Dated obligations, trigger deadlines and general obligations, plus risk allocation, gaps and ambiguities, and deviations from the norm, from Contracko's [AI analysis](https://contracko.com/features/ai-contract-analysis) of each agreement

Where it lives

- Folder, more than a label, because a contract added to one [inherits that folder's access settings](https://contracko.com/docs/folders)

Governing law, jurisdiction and other terms you track are not standard extracted fields. Add them as custom fields on the contract type and the extraction fills those too, which is how you get a jurisdiction column you can sort by.

Two things stay your job: check important values against the document, especially where an amendment changes the original, and ask the assistant to read the saved record back rather than trusting a summary in the chat.

## Contract types decide what gets captured

The list above is the standard set. What makes it yours is the contract type, the shape of the record: a lease and a SaaS subscription need different fields, and the type is where you say so.

There is no fixed catalogue to pick from. You create the types your business uses and rename them later if the naming drifts, which applies to every contract already using that type. Deleting a type leaves its contracts alone and clears the field.

Each type carries [custom fields](https://contracko.com/docs/custom-fields) as text, number, date, yes/no, currency, percentage or a dropdown of set options, each with a label, help text and whether it is required. Rooms on a lease, license counts and service tiers on a subscription, governing law if your team tracks it. Extraction fills those fields too, so the type is how you decide what gets pulled out of every agreement of that kind.

Set it up in the app, or ask the assistant to do it while it imports: write access covers creating contract types and counterparties, and organizing types, custom fields and folders. Agree the type and its fields on the first agreement of a kind, then let the rest of the pile land in the same shape.

## Questions to ask once they are in

Ask in your own words. These tend to earn their keep in the first week.

- Which contracts renew or need notice in the next 90 days? Gives you the decisions that are live, with the terms behind them. Ask for reminders in the same message and you have [renewal reminders running from your assistant](https://contracko.com/blog/contract-renewal-reminders-with-mcp).
- Which of these agreements has no end date recorded? Shows the gaps, which is where a silent renewal hides.
- Create a folder for insurance policies and file the right contracts into it. Turns a filing plan into filing, with the folder's access settings applied to whatever lands in it.
- Add a governing law field to our supplier agreements and fill it from each document. Extends the type, then populates it across the contracts already filed.

## Why not just paste contracts into chat

Pasting a document into a chat window buys you one answer in one conversation. Nobody else can see it, the same question next quarter starts from scratch, and there is nothing to attach a reminder to. Importing puts the document and its extracted fields in one record, so the answer is still there in three months, a colleague can find it, and a deadline can be set against it. That is the difference between a summary and a shared source.

## Connect it and ask one question

Open your assistant's connector or MCP settings and add the Contracko endpoint:

```
https://app.contracko.com/mcp
```

Or let your assistant do the setup. Paste this line into the chat:

```
Fetch and follow the setup instructions for Contracko MCP at https://contracko.com/mcp/install/prompt.md
```

Either way you finish by signing in through your browser (OAuth). No account yet? Start a free trial from that same sign-in screen, no credit card required, and see [pricing](https://contracko.com/pricing) for plan detail; every plan includes the MCP server at no extra cost.

Claude, ChatGPT, Grok and Grok Bot all take the address in their connector settings. Using a coding agent? The same endpoint goes in its own configuration, for example claude mcp add --transport http contracko https://app.contracko.com/mcp in Claude Code, and [the setup documentation](https://contracko.com/docs/mcp-server) has the command for Codex CLI, Cursor and the rest.

Importing creates records, so tick write access when you sign in. Read access alone is enough for questions, and nothing gets created until you approve the plan your assistant shows you. Then attach a few agreements and ask:

> Import these and file each under the right counterparty.

## You stay in control

You pick read or write access at connection time. The assistant acts as you, inside the workspace you chose, and can never exceed your own permissions, so anything you cannot open in Contracko it cannot open either. Write actions pass your client's approval step before they run, and you can revoke the connection at any time.

Created and updated records land in activity history labelled as coming from MCP. The [contract management MCP page](https://contracko.com/mcp/contract-management) has the full picture.

## Frequently asked questions

### Do I need to code?

No. You paste one address into your assistant's settings, sign in, and ask in plain language. If you do write software and need bulk document extraction through a governed connection, the [parsing MCP server](https://contracko.com/mcp/parsing) is the developer route, with credits, batch validation and structured results.

### Which assistants work today?

Claude from Anthropic, through the desktop and web custom connector. ChatGPT from OpenAI, through its own connector settings, though on a Pro account developer mode is read-only, so it can answer but not import. Grok from xAI, by adding the address as a custom connector at grok.com/connectors. Grok Bot, xAI's computer-use agent, takes a custom MCP server the same way, subject to your team's MCP policy. Cursor installs in one click. In the terminal: Claude Code, Codex and Codex CLI. The Gemini app does not support custom MCP servers. Microsoft 365 Copilot reaches Contracko only through a read-only connector a Microsoft 365 admin enables once it is listed in the Connectors Gallery, so it cannot import.

### Are my contracts used to train AI models?

Not by Contracko, which holds multiple Zero Data Retention agreements with AI providers. The client you connect is a separate provider, so turn off model training in its settings before you point it at real agreements.

### What happens to a contract already in Contracko?

Ask the assistant to check first. It can search the workspace for an existing record and counterparty, show you what it intends to file, and wait for your approval before anything changes, which is where you catch a duplicate. Nothing is imported without that approval.

## Sources

Contracko. [Contract management MCP](https://contracko.com/mcp/contract-management): import, filing, access and activity history.

Contracko. [MCP server documentation](https://contracko.com/docs/mcp-server): per-client setup, endpoint, read and write access, supported assistants.

Contracko. [Contract dates](https://contracko.com/docs/contract-dates): end dates, renewal and notice as separate inputs.

Contracko. [Folders](https://contracko.com/docs/folders): inherited access settings.

## Get started with Contracko

Take the hassle out of contract and subscription management. Contracko empowers you to stay organized, on time, and in control. Start simplifying today.

[Start 7-day free trial](https://app.contracko.com/register?appLanguage=en)

Book demo