# Agile CRM MCP connector

The Agile CRM connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent find, update, tag and score your Agile CRM contacts and companies, with every change kept inside your own access and written to an audit log.

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

## Facts

| | |
| --- | --- |
| Application | Agile CRM |
| Category | CRM |
| AI tools | 72 |
| 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 Agile CRM is connected

- Show me notes, tasks and deals for Dana Ruiz before my call
- Tag everyone from the Austin trade show list as event lead
- Which contacts scored above 80 are owned by Priya this month?

## Connect Agile CRM in Elaichi

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

1. Open Connections, choose Add connection, and pick Agile CRM.
2. Optionally set Share with, then press Connect.
3. Paste an Agile CRM API key. One person generates a token in Agile CRM 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 Agile CRM tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

## Agile CRM 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`.

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

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

## Agile CRM 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 Agile CRM 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 Agile CRM 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 Agile CRM through Elaichi

### Catch the contact up after a call

Sales. Tell the agent what changed on the call and it updates the Agile CRM contact, adjusts the lead score and pulls up the deals attached to that person so nothing waits until Friday.

### Prepare for a meeting in one ask

Sales. Ask for everything on a contact before you dial and get their notes, open tasks and linked deals from Agile CRM in one answer.

### Tag a whole list after an event

Marketing. Hand over the email addresses from a trade show or webinar and the agent finds each Agile CRM contact, adds the campaign tag and nudges the score.

### Find the caller by phone number

Support. When someone rings in, search Agile CRM by phone, see who owns the contact and read the last notes before you answer their question.

### Reassign contacts when territories change

Sales operations. Filter Agile CRM contacts by region, tag or owner and move them to the right rep in bulk, with every change recorded.

### Keep account records clean

Customer success. Star the accounts that matter, add a missing property, drop a stale tag or remove a duplicate contact from Agile CRM without opening the app.

## Elaichi vs Zapier MCP vs Composio for Agile CRM

All three can connect Agile CRM 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 Agile CRM tools | Allow or restrict single Agile CRM 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 Agile CRM 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 Agile CRM to Claude?

Two steps. In Elaichi, choose Agile CRM and paste in an API key from your Agile CRM admin settings, there is no OAuth app 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 with your Elaichi account and Agile CRM contacts, companies and deals are available in Claude.

### Does Agile CRM work with ChatGPT and Cursor as well as Claude?

Yes. Once Agile CRM is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Agile CRM once and every client uses it.

### What can an AI agent actually do with my Agile CRM data?

It can find an Agile CRM contact by name, email or phone, create a new one, update fields, add or remove tags, change the owner, star a record and raise or lower the lead score. It can read a contact's notes, tasks and deals, filter contacts by whatever you describe, and list your companies. Short, specific asks such as "tag Dana Ruiz as renewal" work better than long paragraphs.

### Does connecting Agile CRM give the AI access to everything in my account?

No. The connection can only reach what the Agile CRM key it was set up with is allowed to see, and each person still signs in to Elaichi as themselves, so their calls run under their own Elaichi role. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Agile CRM already allows.

### Can my team share one Agile CRM connection?

Yes. One person connects Agile CRM in Elaichi and shares it with a team, and nobody else ever sees or handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who searched, tagged or updated each Agile CRM contact.

### Can I stop an agent from deleting or changing things in Agile CRM?

Yes. Restrictions in Elaichi work per action, so you can allow reading Agile CRM contacts while restricting deleting a contact or changing its owner, and you set them on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an Agile CRM connection when someone leaves?

Offboarding that person in Elaichi ends their access to Agile CRM at once, in every client they used. A shared Agile CRM connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Agile CRM once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

### Does the Agile CRM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Agile CRM 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 Agile CRM?

Yes. Both let Claude, ChatGPT or Cursor use Agile CRM. 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 Agile CRM call.

### How is Elaichi different from Composio for Agile CRM?

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 Agile CRM: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 72 Agile CRM tools

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

- **List all Agile CRM contacts** (List). List contacts in Agile CRM ordered by creation time. Returns contact objects with id, type, lead_score, star_value, tags, tagsWithTime, properties, created_time, and updated_time. Send the Accept: application/json header for JSON responses (XML is the default).
- **Create a Agile CRM contact** (Create). Create a contact in Agile CRM. Returns the created contact object including id, type, lead_score, star_value, tags, properties, created_time, and owner details. Required: properties (the first_name SYSTEM property is mandatory).
- **Agile CRM contacts update star value** (Update). Update the star rating of a single contact in Agile CRM (max value 5). Returns the updated contact values (id, star_value). Does not affect other fields. Required: id, star_value.
- **Agile CRM contacts update tags** (Update). Add tag values to a single Agile CRM contact without affecting other fields. Returns the updated contact object. Tags must start with a letter; only underscore and space are allowed as special characters. Required: id, tags.

- **Agile CRM contacts delete tags** (Delete). Delete tags from a contact or company in Agile CRM by id. Returns the remaining tags on the contact as a list. Required: id and tags.
- **Agile CRM contacts search by email** (Search). Get a single contact in Agile CRM by email address. Returns the contact object including id, type, tags, lead_score, star_value, properties, and owner. Required: email.
- **Agile CRM contacts search by emails bulk** (Search). Search multiple contacts in Agile CRM by a list of email addresses. Returns matching contact records including id, type, tags, lead_score, star_value, properties, and owner. Required: email. Sent as application/x-www-form-urlencoded. Form field: email_ids (JSON array as a string, e.g. ["a@x.com","b@x.com"]).
- **Agile CRM contacts search** (Search). Search contacts or companies in Agile CRM by keyword across default fields and searchable custom fields. Returns matching records including id, type, tags, lead_score, star_value, properties, and owner. Required: q, page_size, and type.
- **Agile CRM contacts add tags by email** (Add). Add tags to an Agile CRM contact found by email address. Returns an array of the added tags ({tag, createdTime, availableCount, entity_type}); the README says 204, but the live API returns 200 with this array. Required: email and tags. Sent as application/x-www-form-urlencoded. Form fields: email (string), tags (JSON array as a string, e.g. ["vip"]).

- **Agile CRM contacts delete tags by email** (Delete). Delete the specified tags from an Agile CRM contact identified by email. Returns an empty 204 response on success. Required: email, tags. Sent as application/x-www-form-urlencoded. Form fields: email (string), tags (JSON array as a string, e.g. ["vip"]).
- **Agile CRM contacts add score by email** (Add). Adjust an Agile CRM contact's lead score by email — pass a positive number to increase it or a negative number to subtract from the existing score. Returns the updated contact object including id, type, lead_score, tags, and properties. Required: email, score. Sent as application/x-www-form-urlencoded. Form fields: email (string), score (number).
- **Agile CRM contacts add property** (Add). Add or update a single property field on an Agile CRM contact identified by email. Returns the updated contact object including id, type, lead_score, tags, and properties. Required: email, type, name, value.
- **Agile CRM contacts change owner** (Action). Change the owner of a contact. Sent as application/x-www-form-urlencoded. Required: owner_email, contact_id. Returns the updated contact; if no user has owner_email, Agile CRM returns a 'user does not exist' message.
- **Agile CRM contacts search by phone** (Search). Get an Agile CRM contact by phone number. Returns the matching contact object including id, type, lead_score, tags, properties, and owner. Required: phone_number.
- **Agile CRM contacts dynamic filter** (Action). Retrieve Agile CRM contacts, companies or deals by a dynamic filter. Set filterJson.contact_type to PERSON (contacts), COMPANY (companies) or OPPORTUNITY (deals). Returns matching records. Requires filterJson. Sent as application/x-www-form-urlencoded. Form fields: page_size, global_sort_key (e.g. -created_time), filterJson (JSON as a string, e.g. {"rules":[{"LHS":"tags","CONDITION":"EQUALS","RHS":"lead"}],"or_rules":[],"contact_type":"PERSON"}).

- **Agile CRM contacts list tasks** (List). List Agile CRM tasks related to a specific contact, sorted latest first. Returns task records including id, type, priority_type, due, is_complete, subject, status, and taskOwner. Requires contact_id.
- **Agile CRM contacts list notes** (List). List Agile CRM notes related to a specific contact. Returns an array of note records. Requires contact_id.
- **Agile CRM contacts delete note** (Delete). Detach a specific note from a specific Agile CRM contact. Returns 204 with no body on success. Requires contact_id and note_id.

- **Agile CRM contacts list deals** (List). List Agile CRM deals related to a specific contact. Returns an array of deal records including id, name, milestone, expected_value, pipeline_id, close_date, and probability. Requires contact_id.
- **Agile CRM contacts update lead score** (Update). Update the lead score of a single contact in Agile CRM. Returns the updated contact values (id, lead_score). Does not affect other contact fields. Required: id, lead_score.
- **Get single Agile CRM contact by ID** (Get). Get a single Agile CRM contact by id. Returns the contact object including id, type, lead_score, star_value, tags, tagsWithTime, properties, created_time, and updated_time. Required: id.
- **Delete a Agile CRM contact by ID** (Delete). Delete a single contact in Agile CRM by id. Returns an empty 204 response on success. Required: id.
- **Agile CRM contacts partial update** (Update). Update or add custom property fields of a contact in AgileCRM without affecting other fields. Properties whose subtype matches an existing phone, website, or email override that value. Lead score, star value, and tags are not supported by this endpoint. Returns the updated contact object including id, type, created_time, and 4 more fields.…
- **List all Agile CRM companies** (List). List Agile CRM companies. Sent as a form POST (application/x-www-form-urlencoded) with page_size, cursor and global_sort_key as form fields; the connector adds page_size and cursor for you. The cursor for the next page is on the last company in the list. Returns company records with id, type, properties, owner and created_time.

- **Create a Agile CRM company** (Create). Create a company in Agile CRM. Returns the new company object including id, type, created_time, updated_time, star_value, lead_score, tags, and properties. Required: type (must be COMPANY), properties (must include a SYSTEM `name` property).
- **List all Agile CRM deals** (List). List Agile CRM deals. Returns the deal records including id, name, contacts, expected_value, milestone, probability, close_date, pipeline_id, and owner.
- **Get single Agile CRM deal by ID** (Get). Get a single Agile CRM deal by id. Returns the full deal object including id, name, contacts, expected_value, milestone, probability, close_date, pipeline_id, and owner. Required: id.
- **Create a Agile CRM deal** (Create). Create a new deal in Agile CRM. Returns the created deal with id, name, contacts, expected_value, milestone, probability, close_date, pipeline_id, and owner. The milestone name must match one defined in the website and is case sensitive.
- **Agile CRM deals create by email** (Create). Create a new deal in Agile CRM and link it to a contact by email. Returns the created deal with id, name, contacts, expected_value, milestone, probability, close_date, pipeline_id, and owner. Required: email. The milestone name must match one defined in the website.
- **Delete a Agile CRM deal by ID** (Delete). Delete an Agile CRM deal by id. Returns an empty 204 response on success.
- **Agile CRM deals bulk delete** (Delete). Delete multiple Agile CRM deals. Returns 204 with no body on success. Required: ids. Sent as application/x-www-form-urlencoded. Form field: ids (JSON array of deal ids as a string, e.g. ["123","234"]).

- **Agile CRM deals list by milestone** (List). List deals from the default Agile CRM track grouped by milestone. Returns an object keyed by milestone name (e.g. "Lost", "Won"), each holding an array of deal objects with id, name, milestone, expected_value, pipeline_id, probability, close_date, owner and created_time.

- **Agile CRM deals list by pipeline grouped** (List). List deals from a specific Agile CRM track grouped by milestone. Returns an object keyed by milestone name, each holding an array of deal objects with id, name, milestone, expected_value, pipeline_id, probability, close_date, owner and created_time. Required: pipeline_id.

- **Agile CRM deals list by pipeline** (List). List deals from a specific Agile CRM track. Returns an array of deal objects including id, name, milestone, expected_value, pipeline_id, probability, close_date, owner, and created_time. Required: pipeline_id.
- **Agile CRM deals list my deals** (List). List deals owned by the current user in Agile CRM. Returns an array of deal objects including id, name, milestone, expected_value, pipeline_id, probability, close_date, owner, and created_time.
- **Agile CRM deals remove contacts** (Delete). Remove contacts from a deal in AgileCRM. Returns the updated deal object with its id, name, milestone, expected_value, contact list, and owner. Required: id, contact_ids.
- **Agile CRM deals partial update** (Update). Update selected fields of a deal in AgileCRM without overwriting other fields. Returns the updated deal object including its id, name, milestone, expected_value, contact list, and owner. Required: id.
- **Create a Agile CRM note** (Create). Create a note and relate it to contacts in Agile CRM. Returns the created note object including its id, created_time, subject, description, and entity_type. Required: subject and description.
- **Agile CRM notes add to contact by email** (Add). Add a note to an Agile CRM contact identified by email address. Returns 204 with no body on success. Sent as application/x-www-form-urlencoded. Form fields: email (string), note (JSON as a string, e.g. {"subject":"Call","description":"..."}).

- **Agile CRM notes create to deal** (Create). Create a note on an Agile CRM deal. Returns the deal object, with the new note in its notes array. Required: subject and description. Use deal_ids to choose the deal(s).

- **Agile CRM notes list for deal** (List). List notes related to a specific deal in Agile CRM. Returns an array of note records; each record includes id, created_time, subject, description, and entity_type. Required: deal_id.
- **Agile CRM notes bulk delete** (Delete). Delete notes of a specific Agile CRM deal. Returns 204 with no body on success. Sent as application/x-www-form-urlencoded. Form field: ids (JSON array of note ids as a string, e.g. ["5641751750508544"]).

- **Agile CRM notes update deal note** (Update). Update a note attached to an Agile CRM deal. Returns the deal object the note belongs to. Required: id, subject, description.

- **Agile CRM tasks list pending** (List). List pending Agile CRM tasks whose due date is within num_days days from today. Returns an array of those task objects including id, type, priority_type, due, subject, status, and taskOwner. Required: num_days.
- **List all Agile CRM tasks** (List). List Agile CRM tasks filtered by type, owner, pending state, criteria, and page_size. Returns an array of task objects including id, type, priority_type, due, subject, status, and taskOwner.
- **Get single Agile CRM task by ID** (Get). Get a single Agile CRM task by id. Returns the task object including its id, type, priority_type, due, subject, status, contacts, notes, and taskOwner. Required: id.
- **Create a Agile CRM task** (Create). Create a new task in Agile CRM. Returns the created task object including its id, type, priority_type, due, subject, status, contacts, notes, progress, and taskOwner. Required: type, priority_type, status, due, subject.
- **Agile CRM tasks create by contact email** (Create). Create a new task in Agile CRM related to the contact with the given email. Returns the created task object including its id, type, priority_type, due, subject, status, contacts, notes, and taskOwner. Required: email, type, priority_type, status, due, subject.
- **Delete a Agile CRM task by ID** (Delete). Delete a task in Agile CRM by id. Returns an empty 204 response on success. Required: id.
- **Agile CRM tasks list all** (List). List all Agile CRM tasks in the domain, ordered by creation time. Returns task records including id, type, priority_type, status, subject, due, is_complete, progress, created_time, and taskOwner.
- ...and 22 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
