Agiloft MCP connector
Connect Agiloft to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or the Elaichi Agent can find contract records, read attachments, update fields, and run saved searches, with every action logged against the person who asked.
- Connects with an API key
- Free 14-day trial
- No credit card
Which contracts renew in the next 90 days?
Working in Agiloft with Elaichi
-
List all Agiloft attachments
-
Get single Agiloft attachment by ID
-
List all Agiloft record IDS
How to connect Agiloft to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Agiloft MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Agiloft MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Agiloft MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Agiloft MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Agiloft MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Agiloft to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Agiloft through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Agiloft is logged.
-
Legal
Find every contract renewing this quarter
Ask for the agreements with renewal dates in the next ninety days and get the list straight from Agiloft, with the counterparty and owner on each record.
-
Procurement
Catch the supplier record up after a call
Say what changed on the call and have the supplier contract record in Agiloft updated with the new term, the pricing note, or the new contact.
-
Sales
Check where a customer agreement stands
Before a renewal conversation, pull the customer's contract record and its signed attachment from Agiloft without opening the application.
-
Finance
Pull signed agreements for an audit
List the attachments on a set of contract records in Agiloft and hand the signed copies to the auditor in one go.
-
Operations
Run a saved search and explain it
Run the saved search the team already maintains in Agiloft and get the results summarized in plain language.
-
Compliance
Lock a record while it is reviewed
Lock a contract record in Agiloft while legal reviews it, then unlock it when the review closes, so nobody edits it mid-review.
Try asking
- “Which contracts renew in the next 90 days?”
- “Attach the signed MSA to the Acme contract record”
- “Run the expiring NDAs saved search and summarize it”
What connecting Agiloft gets you
6 screens from Elaichi, each doing one job for your Agiloft account.
Ask Elaichi to work across your apps.
Which contracts renew in the next 90 days?
Attach the signed MSA to the Acme contract record
Run the expiring NDAs saved search and summarize it
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Agiloft a question, get the contract record.
Three starter prompts pull live records, attachments, and saved searches from Agiloft in plain language.
Copy the endpoint
AI apps
One endpoint brings Agiloft to every AI client.
Claude, ChatGPT, and Cursor reach Agiloft through one governed endpoint, no SDK or shared key.
Tool catalog
22 Agiloft tools, no custom code to write.
Records, attachments, tables, saved searches, locks, and action buttons, all cataloged and ready.
Toolboxes
Every team gets its own Agiloft toolbox.
Legal, Procurement, and Sales each see the Agiloft tools their work needs, scoped by team.
Shared connections
Share an Agiloft connection, never the API key.
One person connects Agiloft, teammates work through it, and nobody else ever sees a credential.
Audit log
Know who touched which Agiloft record, and when.
Every call lands in an append-only log with who, what happened, type, and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Agiloft digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch records
Agiloft
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Agiloft
Queued
Workflows
A schedule drafts the renewal digest, you approve.
Agiloft records are fetched, grouped, drafted into a digest, approved by a person, and posted back.
Agiloft health
Refreshed 4 minutes ago · every 15 minutes · from the records collection
Records
1,284 ↓ 12%
Attachments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Records created
Last 14 days
By team
Share of activity
Legal 34%
Procurement 27%
Sales 21%
Finance 18%
Collections and dashboards
Agiloft contract numbers, computed, with no model involved.
Four metrics, fourteen days of records created, and a breakdown by team, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Agiloft
All three can connect Agiloft to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Agiloft tools | Allow or restrict single Agiloft tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Agiloft call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Agiloft tools for your AI agents
22 tools are ready to call through Elaichi's MCP endpoint the moment you connect Agiloft, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Agiloft to Claude?
Two steps. First connect Agiloft in Elaichi, which asks for your Agiloft API key, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Agiloft is available in Claude.
Does Agiloft work with ChatGPT and Cursor as well as Claude?
Yes. Once Agiloft is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. You connect Agiloft once and every client picks it up.
What can an AI agent actually do with my Agiloft data?
It can search contract records in Agiloft, open a record and its attachments, create or update records, run the saved searches your team already keeps, press a workflow action button, and lock or unlock a record during review. It can also list the tables in your Agiloft knowledgebase so it knows where things live. Short, concrete asks like "show me NDAs expiring in March" work better than long paragraphs.
Does connecting Agiloft give the AI access to every table and record?
No. The agent works inside the access of the Agiloft account that was connected, so it sees only the tables and records that account can see. Elaichi can narrow that further with roles and restrictions, and it never widens what Agiloft itself allows.
Can I stop an agent from deleting or changing things in Agiloft?
Yes. In Elaichi you restrict individual actions on Agiloft, such as deleting a record or an attachment, for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to an Agiloft connection when someone leaves?
Offboarding that person in Elaichi ends their access to Agiloft through every client at once. A shared Agiloft connection keeps working for everyone else on the team. If you want Agiloft gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client.
Does the Agiloft MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Agiloft is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Agiloft?
Yes. Both let Claude, ChatGPT or Cursor use Agiloft. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Agiloft call.
How is Elaichi different from Composio for Agiloft?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Agiloft: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Agiloft in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot