AI contract management agent with Town
Take a supplier framework, such as the fictional Marlow Logistics agreement used in this guide, that renews on 1 February unless you give notice by 3 December. An artificial intelligence (AI) contract management agent with Town is built to put that date in front of you in time. Town is the AI work assistant from Town.com, Inc., and your assistant there is called a Townie. Connect it to Contracko, give it a few routines, and the Townie gathers contracts from your inbox and cloud storage, keeps a central contract repository up to date and flags what needs a decision. Contracko does the expert part: AI contract analysis, the dates, the reminders and the risk review.
This guide connects the Contracko Model Context Protocol (MCP) server to Town, gives your Townie a contract skill and sets up five routines that run while you work on something else.
Why contracts deserve their own Town routines
Town is built around one assistant that already reads your email, calendar and files. What turns it into a contract agent is a standing job: routines that run on a schedule or on an event, and a skill that tells it how the job is done. Contract work fits that shape well. It has its own sources, its own deadlines and a steady trickle of new documents.
For a person, the job covers the lease, the mortgage, insurance policies and the subscriptions that renew quietly every year. For a business, the Townie behaves like an in-house contract manager. It picks up signed agreements, files them, adds the counterparty details and reminds the right people before notice dates.
In this setup, reading the agreements is Contracko's job. Its AI pulls out the terms and analyses the risk, and the Townie works from those results and the clause text that comes back with them. The Townie's routines carry everything around that: mail and Drive, Dropbox or Box searches for new files, uploads, tidy contract types and folders, counterparty contacts, reminders and the weekly note to you.
If the connection itself is new to you, start with what a contract management MCP server is.
What a Town contract agent looks like
An illustrative one-time routine, using fictional companies and data. The files include a statement of work (SOW) and a data processing agreement (DPA). The routine's instructions:
Import the contracts in the Dropbox folder "Contracts 2026" into Contracko and file them by supplier or client.
The Townie reports back:
| File | Contract type | Folder | Status |
|---|---|---|---|
| Marlow Logistics framework.pdf | Framework agreement | Suppliers / Marlow | Imported |
| Pinecrest Studio SOW 2.pdf | Statement of work | Clients / Pinecrest | Imported, type changed from "Other" |
| Harbour Street office lease.pdf | Office lease | Facilities | Imported |
| Ostrava Cloud DPA.docx | Data processing agreement | Suppliers / Ostrava | Imported, no end date found |
Its report adds that Pinecrest's statement of work first came in as "Other", so it changed the type. It also notes that the Marlow framework renews automatically on 1 February, with notice due by 3 December.
Connect Contracko to your Townie
Contracko lists no one-click Town install, so the documented route is Town's custom integration. Town documents custom integrations as tools you switch on inside routines, so every prompt in this guide is written as routine instructions. Asking your Townie in chat should work too, but nobody has tested Contracko from a plain Townie chat yet.
This setup follows Town's and Contracko's published documentation. Nobody has yet tested the whole pairing end to end, from sign-in to every routine below, so treat the results described here as what each routine is set up to do. Run your first routine by hand, then check its run in Town and the new records in Contracko before you rely on it.
Add the Contracko MCP server
Town connects to outside tools through the Model Context Protocol (MCP), the open standard AI assistants use to work with other software. Town's docs call these custom integrations. The Contracko MCP server lives at one address:
https://app.contracko.com/mcp
- In Town, open Integrations and choose Add an integration.
- Paste the address above as the server web address (URL).
- When Contracko asks you to sign in, Town runs the sign-in for you. Sign in to Contracko and approve.
The Contracko MCP page also offers a one-line setup prompt that lets an agent do the setup itself:
Fetch and follow the setup instructions for Contracko MCP at https://contracko.com/mcp/install/prompt.md
Nobody has tested that prompt in Town, and Town documents only the Integrations route for custom servers, so use the steps above.
When Contracko asks what to allow, give your Townie read and write access to your contracts from the start. Read access alone lets it answer questions. Write access is what lets it import, file, fix types and set reminders, which is the whole point. Town's own approval settings, covered under the skill below, decide how much of that runs without asking you.
Contracko has two products, and the sign-in screen shows both:
- Contract management holds the repository itself, with contracts, dates, reminders, folders, analysis and reports. Your Townie works here, and nothing here draws on Parser credits.
- Contracko Parser turns large batches of documents into structured data, outside the repository. A contract agent has no use for it, so leave it unticked.
No Contracko account yet? Start a free trial with no credit card from pricing.
Turn Contracko on in each routine
Town's docs describe MCP servers as something you switch on per routine. Open a routine, find the MCP servers card, choose Add or manage MCP servers and tick Contracko. Do this for every contract routine below. With Contracko ticked, the routine can work through Town MCP.
Teach your Townie a contract skill
A Town skill is a reusable set of instructions the Townie pulls in for one kind of task. You create one by asking for it. Contracko publishes its own instructions for agents as one skill, contracko, in the open Contracko skills library at github.com/contracko/contracko-skills. Paste its instructions into the chat with this:
Create a skill called "Contracts" from the instructions I pasted. You run our contracts in Contracko with read and write access: import, file and correct them, and keep the repository current. Quote the clause behind every finding. Never delete anything. Tell me what needs a decision, and use this skill in every routine that touches contracts.
New Town routines start in auto mode, so their changes run without asking. In a routine's Tools and permissions panel, Execution mode can switch it to Human in the Loop. That is not a gate on every change: it holds only actions other people would see, such as emails to other people and Slack messages. For a tighter rule, the same panel lets you set a single tool to Ask each time. Town also flags unsafe combinations when you save, such as a routine that reads private data, takes in outside email and can send messages out. Read those warnings before you switch a contract routine on.
Build a contract repository with tracking
A central contract repository with tracking is where your Townie earns its keep. Every agreement sits in one place, and the dates and reminders keep working long after the routine has finished. If the idea is new to you, start with what a contract repository is.
Bring every contract in
Town connects natively to Gmail, Google Drive, Dropbox, Box and Outlook. Connect the ones that hold your contracts, then create a one-time routine with Contracko ticked and these instructions:
Find every signed contract in my Gmail attachments and in Google Drive from the last three years. Import each one into Contracko, wait until every import is done and list anything that failed.
On a three-year mailbox, the routine's list of failures matters as much as its successes, so read it before you move on. Each finished import becomes a contract record, linked to a counterparty Contracko already knows or to a new one. The longer version of this job is in how to import and organise contracts with MCP.
Contracko knows what to extract
Contracko's AI contract analysis pulls the parties, the start, end and renewal dates, notice periods, payment terms and contract values. Each contract type can carry its own custom fields, and extraction fills those as well. The analysis also highlights liabilities, obligations and unusual terms.
Take the Marlow framework. Its end date says when the first term stops, not what happens next. Contracko stores whether it auto-renews, how long each renewal lasts and how many days of notice it needs, so the 3 December deadline follows from the record. Contract dates and auto-renewals explains the fields.
Fix types and file folders
The step people skip is the one that keeps a repository usable. Add it to the import routine, or give it a weekly routine of its own:
Check that every contract imported this week has the right contract type, and change any that are wrong. Then file each contract in the right client, supplier or facilities folder.
To fill a corrected type's own fields, ask for a re-read as a separate step. Contracko re-reads a type's custom fields across its contracts, asks for your approval first and leaves values already saved as they are.
Reminders and your calendar
Once the dates are in, one routine run can set reminders across the whole repository:
Set a reminder 21 days before the notice deadline of every contract that renews automatically, and send it to me and to the contract owner.
The reminders live in Contracko, so they fire whether or not Town runs that day. More prompts are in contract renewal reminders with MCP.
Contracko's calendar feed puts start, end and notice dates into Google Calendar, Apple Calendar or Outlook. This part needs no routine: take the feed address from the Calendar page in Contracko and paste it into your calendar app one time. The calendar setup guide has the steps.
AI contract analysis for any agreement
Contracko works as an AI contract analysis tool for one agreement at a time: what it commits you to, which dates matter, how money moves and what is unusual. Contracko has already analysed the contract, so your Townie answers from that analysis and quotes the sentence behind each point. Read the quoted wording in the agreement before you act on it. Put questions like these in a one-time routine:
Summarise the Marlow Logistics framework in five lines: term, notice period, pricing and anything unusual.
What does the Harbour Street lease require from us before we hand back the keys?
An illustrative answer to the first prompt, with fictional data:
| Point | What Contracko found | Clause |
|---|---|---|
| Term | Two years from 1 February, then yearly | "The initial term is two years from 1 February, after which the Agreement renews for successive one-year periods." |
| Notice | 60 days before renewal, in writing | "Notice of non-renewal must be given in writing no later than 60 days before the renewal date." |
| Unusual | Fuel surcharge set by the supplier alone | "Marlow may adjust the fuel surcharge at its discretion on 14 days' notice." |
For the same job in a chat assistant, see AI contract review with MCP.
AI contract review for risk and obligations
Portfolio review turns the lens around. Instead of one agreement in depth, a routine puts one narrow question to every contract in the repository. A monthly routine suits it, because exposure changes as agreements arrive and renew:
Before the Marlow renewal, show me which logistics and cloud suppliers can end their contract at will while we cannot, and where their liability to us has no cap.
What do we owe clients over the next 60 days, counting deliverables, reports, payments and notices?
An illustrative findings table for the second prompt, with fictional data:
| Due | What we owe | Counterparty | Clause |
|---|---|---|---|
| 5 December | Monthly service report | Pinecrest Studio | "Supplier shall deliver a service report by the fifth day of each month." |
| 15 December | Proof of insurance | Harbour Street landlord | "Tenant shall provide evidence of insurance each year by 15 December." |
| Before any change | 30 days' notice of a new subcontractor | Pinecrest Studio | "Supplier shall give 30 days' written notice before changing any subcontractor." |
Every row carries the sentence it rests on, so you can check each finding in context. Bring in a lawyer where the stakes call for it. For the wider discipline, see contract risk management.
Reports your team will open
Contracko's reports are live views of your account, built for questions such as upcoming renewals, vendor concentration and portfolio risk. A routine can build one for you, so the answer lives in Contracko instead of in a chat message.
Build a Contracko report of our upcoming renewals and tell me when it is ready to review.
A new report starts private. Sharing it with your workspace or named colleagues is a separate step that needs your explicit approval. Because the report reads live data, it shows current renewals whenever someone opens it.
Five workflows to run on a routine
A Town routine runs a job on its own. It can start on a schedule (daily, weekdays, weekly or a custom interval) or on an event, such as an incoming email, a calendar change, a Slack mention or a webhook. Create each routine in Town, tick Contracko on its MCP servers card, and use the prompt below as its instructions.
Town's free plan has no custom routines, and its entry paid plan limits how many you can run and allows only scheduled triggers. The email and Slack triggers need a higher plan, so check Town's plans page before you build all five.
Onboard everything once
Run this once, as a one-time routine. It works for a household's paperwork and for a company's archive.
Go through Gmail, Outlook, Google Drive, Dropbox and Box and collect every agreement that has been signed. Upload them to Contracko one by one and keep checking until Contracko has processed them all. Where Contracko picked the wrong contract type, correct it. Give each household category, client and supplier its own folder and move the contracts in. Finish with a short report: the number uploaded, the folder each one went to and every file that would not upload.
Watch a folder for new contracts
Trigger: schedule, weekdays at 07:00.
Look in the Drive folder "Signed agreements" for anything new since this routine last ran. Hand each new document to Contracko, confirm the upload is processed, correct the contract type if needed and move it to its client or supplier folder. Email me the new contract names, and stay silent on days with nothing new.
Catch signed contracts in your inbox
Start with a one-off audit of your mailbox, as a one-time routine:
Look through my email for signed contracts that arrived as attachments. Upload any that Contracko does not have yet and list what you added.
Then create a routine with a smart email trigger, with the condition "an email arrives with a signed contract attached". Town still runs the routine when it cannot judge a condition, so the instructions check the attachment first:
First check that the attachment really is a signed contract, and stop if it is not. Import it into Contracko and wait until the import has finished. Check the contract type and file it in the right folder. From the email thread, add the counterparty's contact person, email address and role to the counterparty in Contracko. Send me one line with what you imported.
Get a weekly deadline digest
Trigger: schedule, weekly on Monday at 08:00.
Ask Contracko which agreements reach a notice deadline or an end date within 60 days. For each, give me the date and the choice in front of me: renew, renegotiate or cancel. Below that, flag last week's uploads that are missing an end date or a contract type. Email it to me as a single digest.
Share reports with your team
Connect Slack in Town first. Trigger: schedule, monthly on the first weekday at 09:00.
Share the renewals report with your team in Contracko yourself, once. The routine then only posts a pointer to it:
Read the Contracko report of upcoming renewals. Post a two-line summary of the renewals it shows in our #legal Slack channel, and tell people to open the report in Contracko for the detail.
What your Townie can and cannot do
Contracko gives your Townie your own permissions in the workspace you picked at sign-in, and nothing beyond them. Its records and edits carry an MCP label in Contracko's activity history, so you can trace every change.
One Town caveat: team routines always run in auto mode, with no approval step. Build and test a contract routine as your own routine before you share it with a team.
Removing contracts stays a job for people in the Contracko app. Through MCP, a Townie can delete only custom dates and reminders. Contracts, their documents, folders, counterparties and contract types have no delete action over the connection.
To cut Town off, open Settings in Contracko, go to Integrations and remove it under MCP Connections. The MCP server documentation explains the access options in full.
Contracko does not train models on your contracts. Town says nothing you connect trains a model by default, and states it is System and Organization Controls (SOC) 2 Type 2 compliant. Contract text you discuss still passes through Town, so check its settings before you connect real agreements.
Why a connection beats pasting
Paste a contract into a chat and the Townie sees one file, frozen at that moment. It has no way to know that an amendment replaced clause 9 last month. Connected to Contracko, it asks the repository each time, so the dates and analysis it reports are the ones on record today. The Monday digest is only as current as that source.
Frequently asked questions
How do I connect Town to a contract management MCP server?
In the Town AI assistant, open Integrations, add https://app.contracko.com/mcp as a custom integration and sign in to Contracko in your browser. Then tick Contracko on each routine's MCP servers card, because Town MCP access is switched on per routine. No code is needed. Chat use should work as well but is untested, so this guide runs everything through routines.
How do businesses track contract renewal dates automatically?
The dates have to come from the contracts themselves, not from someone's memory. In this setup, Town routines feed new agreements into Contracko, Contracko's AI reads the renewal terms and notice periods, and reminders fire from Contracko on their own schedule. The Monday routine adds a second net by listing what falls due in the next 60 days.
Can AI read contracts reliably?
You can ask your Townie to quote the clause behind any answer, so you can check it against the wording. AI can still misread a clause, so confirm important terms in the agreement itself.
Can I try free AI contract review before setting up the agent?
Yes. Contracko's free AI contract review tool checks a single document.
Does my Townie use Parser credits?
No. A contract agent uses Contracko's contract management tools, which never spend Parser credits. Parser is a separate product for bulk document processing.
Which Town plan do I need?
Town's free plan has no custom routines, so this guide needs a paid plan. Custom routines start on the entry paid plan, which caps the number of routines and allows scheduled triggers only. Email triggers, Slack triggers and unlimited routines need a higher individual plan, or a paid team plan for team-owned routines. Town lists its integrations as included on every plan but does not single out custom MCP servers, so confirm on its plans page before you buy.
Sources
- Town. Custom Integrations (MCP): adding a custom MCP server by URL, OAuth and enabling servers per routine.
town.com/docs/integrations/mcp-servers - Town. Routine triggers: schedules, email, calendar, Slack and webhook triggers.
town.com/docs/routines/custom-routines/triggers - Town. Skills: creating reusable instructions for your Townie.
town.com/docs/features/skills - Town. Plans and pricing: credits and routine limits.
town.com/docs/billing/plans - Contracko. Contract management MCP server: access and activity history.
- Contracko. MCP server documentation: sign-in, access and managing connections.
Get started with Contracko
Take the hassle out of contract management. Contracko empowers you to stay organized, on time, and in control. Start simplifying today.