Close MCP connector
The Close connector brings leads, contacts, opportunities, calls, emails, and notes from Close into Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent, so each person can ask about their pipeline inside their own Close access, with every request logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which opportunities in the Q3 pipeline haven't had a call this week?
Working in Close with Elaichi
-
Activity search
-
Close product knowledge search
-
Get AI credit usage
How to connect Close to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Close 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.
Close 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.
Close 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.
Close 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.
Close 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 Close 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 Close through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Close is logged.
-
Sales
Prep for a call in one question
Ask for everything on a lead before you dial: the contacts, the open opportunity, the last email thread, and the notes your colleague left. The answer comes from live Close records, not a stale export.
-
Sales
Review what happened on yesterday's calls
Pull the meeting transcripts and call records from the day and get a summary of what each prospect said, what they objected to, and what you promised to send.
-
Sales development
Work a smart view without clicking through it
Ask which leads in a saved smart view have had no activity this week, which status they sit in, and who owns them, then decide where to spend the morning.
-
Sales leadership
Get a pipeline picture before the Monday meeting
Ask how many opportunities sit in each status, which ones moved since last week, and which have gone quiet, totaled by rep or by month.
-
Customer success
Catch up on an account before renewal
Read the full history of a lead in Close, including emails, notes, calls, and tasks, and get a short account summary before you reach out.
-
Finance
Check invoices against closed deals
Look up the invoices attached to a lead in Close, compare them with the won opportunities, and spot anything billed late or not at all.
Try asking
- “Which opportunities in the Q3 pipeline haven't had a call this week?”
- “Summarize yesterday's meeting transcript with Acme and list the follow-ups”
- “Show me leads in the Trial ending soon smart view”
What connecting Close gets you
6 screens from Elaichi, each doing one job for your Close account.
Ask Elaichi to work across your apps.
Which opportunities in the Q3 pipeline haven't had a call this week?
Summarize yesterday's meeting transcript with Acme and list the follow-ups
Show me leads in the Trial ending soon smart view
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your pipeline, get answers from Close.
Live leads, opportunities, and call notes, answered in plain language.
Copy the endpoint
AI apps
Close works in every client through one endpoint.
Claude, ChatGPT, Cursor, Microsoft Copilot, and Microsoft Copilot connect to Close over OAuth, with no SDK or shared API key.
Tool catalog
121 Close tools, ready without writing code.
Leads, contacts, opportunities, calls, emails, notes, and tasks, covered with no custom code.
Toolboxes
Every team gets its own Close toolbox.
Sales, finance, and success each see the Close tools that fit their work.
Shared connections
Share Close access, never share a credential.
One person connects Close; teammates work through it without seeing a login.
Audit log
Every Close request is logged with a name.
When, who, and which lead or opportunity was touched, kept in an append-only log.
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.
Close digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch leads
Close
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
Close
Queued
Workflows
A schedule turns Close activity into real work.
Calls and emails are fetched, grouped, drafted into a digest, approved, and posted back to Close.
Close health
Refreshed 4 minutes ago · every 15 minutes · from the leads collection
Leads
1,284 ↓ 12%
Contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Leads created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales US 27%
Outbound 21%
Customer success 18%
Collections and dashboards
Close pipeline health, computed without a model.
Leads created over 14 days, broken down by team, refreshed on a schedule.
Why connect Close's MCP server through Elaichi
Close builds and runs this MCP server. Elaichi sits in front of it, so Close's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Close's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach Close's tools at the same Elaichi address as every other connected app. Nobody adds Close's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own Close sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Close's server. By default, a tool Close does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to Close
Close builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Close team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Close
All three can connect Close 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 Close tools | Allow or restrict single Close 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 Close 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.
Close tools for your AI agents
121 tools are ready to call through Elaichi's MCP endpoint the moment you connect Close, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Close builds and runs these tools.
No tools match your search.
Questions, answered
How do I connect Close to Claude?
Connect Close in Elaichi first. Close connects over OAuth, so you sign in to Close with your normal login and approve the access; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi and Close is ready to use.
Does Close work with ChatGPT and Cursor as well as Claude?
Yes. Once Close 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 Close once and every client picks it up.
What can an AI agent actually do with my Close data?
It can find leads, contacts, and opportunities in Close, read the calls, emails, notes, tasks, meeting transcripts, and invoices attached to them, and summarize what it finds. It can also total things up, such as opportunities by status or activity by rep, and look at your saved smart views and lead statuses. Short, specific asks tend to work better than long paragraphs, for example a lead name and the question you have about it.
Does connecting Close give the AI access to every lead in my organization?
No. Each person signs in to Close as themselves, so the agent sees only the leads, contacts, and opportunities that person can already see in Close. Elaichi can narrow that further by role or by action, but it can never widen access beyond what Close itself allows the signed-in person.
Can I stop an agent from deleting or changing things in Close?
Yes. Restrictions in Elaichi work per action, so you can allow reading leads and opportunities while restricting anything that edits or removes records in Close. 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 Close connection when someone leaves?
Offboarding that person in Elaichi ends their access to Close through every connected client at once, including Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. A Close connection they shared with a team keeps working for everyone else. If you want Close gone entirely, disconnecting it once in Elaichi removes it from every client.
Does the Close MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Close 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 Close?
Yes. Both let Claude, ChatGPT or Cursor use Close. 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 Close call.
How is Elaichi different from Composio for Close?
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 Close: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Close 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