# 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.

Source: https://elaichi.ai/connectors/agiloft/

## Facts

| | |
| --- | --- |
| Application | Agiloft |
| Category | E-Signature |
| AI tools | 22 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Agiloft is connected

- 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

## Connect Agiloft in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Agiloft.
2. Optionally set Share with, then press Connect.
3. Paste an Agiloft API key. One person generates a token in Agiloft and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Agiloft tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Agiloft MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Agiloft MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Agiloft tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Agiloft through Elaichi

### Find every contract renewing this quarter

Legal. 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.

### Catch the supplier record up after a call

Procurement. 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.

### Check where a customer agreement stands

Sales. Before a renewal conversation, pull the customer's contract record and its signed attachment from Agiloft without opening the application.

### Pull signed agreements for an audit

Finance. List the attachments on a set of contract records in Agiloft and hand the signed copies to the auditor in one go.

### Run a saved search and explain it

Operations. Run the saved search the team already maintains in Agiloft and get the results summarized in plain language.

### Lock a record while it is reviewed

Compliance. Lock a contract record in Agiloft while legal reviews it, then unlock it when the review closes, so nobody edits it mid-review.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Agiloft connection?

Yes. One person connects Agiloft in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Agiloft action.

### 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.

## All 22 Agiloft tools

Every tool below is callable through https://api.elaichi.ai/mcp once Agiloft is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Agiloft access token** (Create). Log in with the connected KB, login and password (EWLogin) and get a JWT access token (default lifetime 15 minutes, up to 60 via the token_expires_in global variable). The connector calls this at connect time and every 10 minutes. The credentials go in the query string; the request is sent with Content-Type text/plain and an empty body, as documented.
- **Agiloft action buttons execute** (Execute). Run an action button on a record (EWActionButton, asynchronous). Returns the record ID and a callback ID to poll with async_operations.lookup.
- **Agiloft async operations lookup** (Action). Check the status of an asynchronous call such as action_buttons.execute (EWAsyncStatus). The status is the HTTP code: 200 completed, 201 queued, 202 in progress, 501 failed, 523 unknown callback ID.
- **List all Agiloft attachments** (List). List the files attached in a file field of a record (EWAttachInfo): position, name and size of each.
- **Create a Agiloft attachment** (Create). Attach a file to a file field of a record (EWAttach, PUT with the file content in the body). Returns the number of files now in the field.
- **Get single Agiloft attachment by ID** (Get). Download one attached file from a file field of a record (EWRetrieve). The id is the file's 0-based position in the field (from attachments.list). The response body is the raw file with the content type it was attached with.
- **Delete a Agiloft attachment by ID** (Delete). Remove one attached file from a file field of a record (EWRemoveAttachment). The id is the file's 0-based position in the field (from attachments.list). Returns the number of files remaining.
- **Agiloft choice lines lookup ID** (Action). Look up the internal ID of a choice-list value (EWGetChoiceLineId), for use in SQL where clauses such as record_ids.list. IDs change when a KB is copied or choice lists are recreated, so look them up at run time.
- **List all Agiloft record IDS** (List). Return the IDs of the records in a table that match a SQL where clause (EWSelect). The clause runs at the database level, so it uses database column names (from the Field Wizard) and choice-line IDs (see choice_lines.lookup_id) rather than labels; record order is not controllable. Security filters are applied automatically.
- **Agiloft record locks lookup** (Action). Get the lock status of a record (EWLock GET): whether it is locked, by whom, and minutes until the lock expires.
- **Agiloft record locks lock** (Action). Lock a record (EWLock PUT) for the connected user so others cannot edit it. The lock lasts for the KB's lock_expiration_time global variable.
- **Agiloft record locks unlock** (Action). Unlock a record (EWLock DELETE). Admin-group users can pass `force` to release a lock held by another user.
- **Create a Agiloft record upsert** (Create). Create or update a record (EWUpsert): if `match_query` matches no record a new one is created, if it matches exactly one that record is updated with the supplied fields, and if it matches several the call fails with 409. Returns the ID of the created or updated record.
- **List all Agiloft records** (List). List records in a table (EWSearch), optionally filtered by an ad hoc query and/or a saved search, returning the requested fields for each record. Pages are 0-based; pass `limit` to page (a limit of 0 returns all records on page 0). Without `field`, only the ID, type and record-ownership fields are returned.
- **Get single Agiloft record by ID** (Get). Read one record (EWRead) by its ID and return all of its field values.
- **Create a Agiloft record** (Create). Create a record (EWCreate) in a table with the supplied field values and return the new record ID. Rules configured on the table run as part of the operation.
- **Update a Agiloft record by ID** (Update). Update a record (EWUpdate) by ID with the supplied field values (only the fields sent are changed) and return the full record after the update.
- **Delete a Agiloft record by ID** (Delete). Delete a record (EWDelete) by ID, applying the chosen strategy to dependent (linked) records. If the strategy cannot be applied the delete fails and the error suggests alternatives.
- **Agiloft records search** (Search). Search records with a natural-language request (EWNLPSearch), e.g. "Active NDAs submitted last month". The tables searched are those the KB's chat search is configured for; results use the same format as records.list.
- **List all Agiloft saved searches** (List). List the saved searches defined for a table (EWSavedSearch): name, label, ID and description. Use the label as `search` in records.list.
- **List all Agiloft tables** (List). List all tables in the KB (EWTable) with their labels and logical names and, unless skip_columns_info is true, their fields (name, label, type). Action buttons, related tables and embedded searches are not included.
- **Get single Agiloft table by ID** (Get). Get one table (EWTable with `table`) by logical name, with all of its fields (name, label, type, linked-field sources). The id is the logical table name, e.g. `contract`.
