Nimble MCP connector
The Nimble connector brings your Nimble contacts, notes, tags and custom fields to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can find, update and annotate contacts in plain language under their own Nimble access.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Nimble contacts have no notes this quarter?
Working in Nimble with Elaichi
-
List all Nimble me
-
List all Nimble contacts
-
Get single Nimble contact by ID
How to connect Nimble to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Nimble 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.
Nimble 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.
Nimble 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.
Nimble 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.
Nimble 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 Nimble 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 Nimble through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Nimble is logged.
-
Sales
Catch a contact up after a call
Tell the agent what was discussed and it writes the note against the right Nimble contact and updates the fields that changed, before the next meeting starts.
-
Sales
Find the contacts worth calling this week
Ask for contacts with a given tag, company or custom field value and get a short list pulled from Nimble, ready to work through.
-
Marketing
Tag a batch of new leads at once
After an event, hand over the list of names and companies and have them created in Nimble and tagged for the follow-up campaign in one pass.
-
Support
Log what a customer told you
Add a note to a customer's Nimble contact while the conversation is still fresh, so sales and account managers see the history without asking.
-
Operations
Keep custom fields tidy and consistent
Add, rename or retire a contact field in Nimble and set which value counts as primary, without clicking through every record by hand.
-
Leadership
Get a quick read on the contact base
Ask how many contacts carry a certain tag or came in this month and get an answer from live Nimble records instead of waiting for an export.
Try asking
- “Which Nimble contacts have no notes this quarter?”
- “Add a note to the Nimble contact for Acme.”
- “Tag every Nimble contact I met last week.”
What connecting Nimble gets you
6 screens from Elaichi, each doing one job for your Nimble account.
Ask Elaichi to work across your apps.
Which Nimble contacts have no notes this quarter?
Add a note to the Nimble contact for Acme.
Tag every Nimble contact I met last week.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Nimble contacts in plain language.
Answers come from live Nimble contacts, notes and tags, not a stale export.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Nimble.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
85 Nimble tools ready without custom code.
Contacts, notes, tags and proceedings, each with its own methods and resources.
Toolboxes
Every team gets its own Nimble toolbox.
Sales, support and marketing each see a curated set of Nimble tools.
Shared connections
Teammates use Nimble without seeing credentials.
Each Nimble connection shows its owner and the teams and members it serves.
Audit log
Every Nimble call is written down.
When, who, what happened, type and resource for each contact and note touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Nimble digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch contacts
Nimble
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
Nimble
Queued
Automations
A schedule drafts your Nimble digest.
Six steps fetch contacts, group them, draft a digest, then post back after approval.
Nimble health
Refreshed 4 minutes ago · every 15 minutes · from the contacts collection
Contacts
1,284 ↓ 12%
Notes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Contacts created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales North America 27%
Marketing 21%
Support 18%
Collections and dashboards
Nimble health counted, not asked for.
Four metrics, 14 days of contacts created, split by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Nimble
All three can connect Nimble 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 Nimble tools | Allow or restrict single Nimble 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 Nimble 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.
Nimble tools for your AI agents
85 tools are ready to call through Elaichi's MCP endpoint the moment you connect Nimble, 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 Nimble to Claude?
Connect Nimble in Elaichi first, which asks for your Nimble API key and nothing else, so there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and Nimble is available in Claude.
Does Nimble work with ChatGPT and Cursor as well as Claude?
Yes. Once Nimble 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 Nimble once and every client sees it.
What can an AI agent actually do with my Nimble data?
It can look up a Nimble contact, create new contacts, update details, assign tags, add and edit notes on a contact, and manage the custom fields your team uses. In practice that means asking for a contact's history before a call, or dictating a note afterwards and having it filed against the right person. Because Nimble exposes many actions, short concrete asks such as add a note to Jane Park at Acme work better than long paragraphs.
Does connecting Nimble give the AI access to everything in my account?
No. The agent works inside the access of the Nimble account whose API key was used, so it can see and change exactly what that person can in Nimble, and nothing more. Elaichi can narrow that further, for example to reading contacts but not deleting them, and it never widens what Nimble itself allows.
Can I stop an agent from deleting or changing things in Nimble?
Yes. In Elaichi you restrict Nimble actions one by one, so you can allow reading and creating contacts while restricting deletion of contacts, notes or fields. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Nimble connection when someone leaves the company?
When you offboard a person in Elaichi, their access to Nimble through every client ends at once. If they had shared a Nimble connection with a team, it keeps working for everyone else until you decide otherwise. Disconnecting Nimble in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in a single step.
Does the Nimble MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Nimble 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 Nimble?
Yes. Both let Claude, ChatGPT or Cursor use Nimble. 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 Nimble call.
How is Elaichi different from Composio for Nimble?
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 Nimble: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Nimble 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