Contract renewal reminders with MCP

Ask your AI assistant which contracts renew or need notice in the next 90 days, see which of them renew automatically, and have reminders set before the window closes. Contracko's MCP server connects your contract workspace to the assistant you already have open, so the answer comes from your own contract records instead of a spreadsheet someone updated last quarter.

What it looks like in practice

MCP, the Model Context Protocol, is an open standard that lets an AI assistant reach tools and data outside its chat window. If that is new to you, start with what a contract management MCP server is. The exchange below is an illustrative example with fictional companies and dates.

Which contracts renew or need notice in the next 90 days?

Contract	Renews	Notice by
Brightline cleaning services	Auto-renews for 12 months	3 December
Vellum payroll software	Auto-renews monthly	28 November
Harbour Point office lease	Auto-renews for 12 months	9 December
Tanner freight agreement	Ends, no renewal	Not required

Three of the four renew unless somebody gives notice. The assistant then offers: shall I set a reminder 30 days before each notice date?

Questions you can ask about renewals

Ask in your own words. These questions produce something you can act on:

• Which contracts renew or need notice in the next 90 days? A dated shortlist with the decision deadline for each agreement.
• Which of our subscriptions renew automatically, and for how long? Separates the contracts that continue by default from those that simply expire.
• What notice does the Brightline contract require, and by when? The recorded notice terms, with Contracko's analysis of that contract behind them.
• Show every Acme agreement with an end date or notice date next quarter. The same review narrowed to one counterparty, contract type, status or folder.
• Which contracts have no end date or notice date recorded? The gaps, which a date-based search cannot return.
• Can you set a reminder 30 days before each notice date? The follow-up saved in Contracko, once you have granted write access.

The same connection also handles AI contract review.

Set up the whole portfolio at once

One question at a time is the small version of this. The assistant works across the portfolio, so the reminder system you would otherwise build contract by contract gets built in one sitting.

Start with an audit, then fix what it finds:

Which of our supplier agreements have no notice date recorded, and which have no reminder set?

That gives you the two lists worth acting on: contracts where the deadline is unknown, and contracts where it is known but nobody will be told. Then work in bulk, narrowed by contract type, counterparty, status or folder:

For every supplier agreement with a notice date, set a reminder 30 days before it. Show me the list before you create anything.

Contracko's write access covers updating fields across contracts and creating reminders in bulk, so one instruction can cover a whole contract type. Ask for the proposed list first, because a mistake repeated across 40 contracts is still 40 mistakes, then run the audit again, which should come back empty.

The same pattern suits any event you track everywhere: an insurance certificate renewal on every policy, or a price-review date on every framework agreement.

Why the notice date matters most

The decision deadline is the notice date, not the end date. An agreement that ends on 31 March with 60 days of notice needs a decision in January, so a reminder tied to the end date arrives after the renewal has effectively been decided for you.

In Contracko, the end date, auto-renewal and termination notice are separate settings, as contract dates and auto-renewals describes. So an end date alone is not evidence of automatic renewal, and a search by date leaves out contracts with no date recorded. Setting a reminder is also an internal follow-up, not the delivery of contractual notice, which stays with whoever owns the agreement.

Why not just paste contracts into chat

Pasting a document into a chat window answers one question about one file, and the answer leaves with the conversation. Nothing remains to warn anyone in November.

A connection changes the unit of work from a document to a portfolio. Your assistant can ask across every contract your account can reach, narrow by counterparty, contract type or status, folder, or by the end and notice dates falling in a window, and read Contracko's analysis of each contract rather than your summary of it. With write access it saves the reminder in Contracko, where colleagues can see it and where it outlives the chat. To keep reminders out of an assistant altogether, contract renewal reminder software covers the same job inside the app.

Connect it and ask one question

Connecting needs no code. In your assistant's connector settings, add the Contracko endpoint:

https://app.contracko.com/mcp

A browser window opens, you sign in to Contracko (this is OAuth), and you choose the workspace. Or let your assistant do the setup: paste this line into the chat instead.

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

No account yet? Create one from the sign-in page the connection opens, or start a free trial with no credit card and see what each plan includes. Every Contracko plan carries the MCP server at no extra cost. Claude, ChatGPT, Grok and Grok Bot all take the address in their own connector settings. Coding agents such as Claude Code, Codex CLI and Cursor read it from their configuration instead, for example claude mcp add --transport http contracko https://app.contracko.com/mcp in Claude Code, and the MCP setup documentation carries the command for each one.

Start with read access: the assistant can answer every question above but cannot change anything. Then ask the first question: which contracts renew or need notice in the next 90 days?

You stay in control

You choose read or write access at connection time. The assistant acts as you, inside the workspace you pick, 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, created and updated records land in activity history labelled as coming from MCP, and you can revoke the connection at any time from Contracko or from the client.

Frequently asked questions

Do I need to code? No. You paste one address into your assistant's connector settings and sign in through your browser. After that you type questions in plain language.

Which assistants work today? Claude from Anthropic, through the desktop and web custom connector. ChatGPT from OpenAI, through its own connector settings. 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, with a one-click install. In the terminal: Claude Code, Codex and Codex CLI. The Gemini app does not support custom MCP servers. Microsoft 365 Copilot is different: a Microsoft 365 administrator has to enable a read-only connector once it is listed in the Connectors Gallery, so you cannot set it up yourself today.

Is my contract data used to train AI models? Not by Contracko, which holds multiple Zero Data Retention agreements with AI providers. Your AI client is a separate provider with its own settings, so turn off model training there before you connect real contracts.

What if reminders already exist, or dates are missing? Ask which contracts in the window already have a reminder, so you add one where it is missing instead of doubling up. For gaps, ask which contracts have no end date or notice date recorded, then fill those in before you trust a 90-day list.

Sources

Contracko. Contract management MCP server: renewal and notice questions, connected assistants, permissions and plan inclusion.

Contracko. MCP server documentation: per-client setup, endpoint, browser sign-in, read and write access, and date searches.

Contracko. Contract dates and auto-renewals: end date, auto-renewal and termination notice as separate settings.

Model Context Protocol. Specification of the open standard behind these connections. modelcontextprotocol.io/specification