# Close MCP connector The Close connector brings leads, contacts, opportunities, calls, emails, and notes from Close into Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person can ask about their pipeline inside their own Close access, with every request logged. Source: https://elaichi.ai/connectors/close/ ## Facts | | | | --- | --- | | Application | Close | | Category | CRM | | AI tools | 121 | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | Native MCP | Yes. Close builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top | | Support for its tools | help.close.com/welcome-to-close-help | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, 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 Close is connected - 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 ## Connect Close in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Close. 2. Optionally set Share with, then press Connect. 3. Approve it in Close. Close's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Close tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Close 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. ## Close 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 today. The plugin directory lives at chatgpt.com/plugins. ## Close 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. ## Connect Close 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 Only Read is granted by default, which is not enough to call a Close tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Close through Elaichi ### Prep for a call in one question Sales. 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. ### Review what happened on yesterday's calls Sales. 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. ### Work a smart view without clicking through it Sales development. 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. ### Get a pipeline picture before the Monday meeting Sales leadership. 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. ### Catch up on an account before renewal Customer success. 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. ### Check invoices against closed deals Finance. 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. ## 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. Endpoint: 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 | $15 per user per month. | 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 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, 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 my team share one Close connection? Yes. One person connects Close in Elaichi and shares the connection with a team, and nobody else ever handles a credential or sets anything up. Each teammate still signs in as themselves, so the audit log names the actual person behind every request to Close. ### 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 blocking anything that edits or removes records in Close. A restricted action is never shown to Claude, ChatGPT, or any other client at all, so no prompt, however worded, can reach it. ### 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, 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, 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. ## All 121 Close tools Every tool below is callable through https://api.elaichi.ai/mcp once Close is connected, subject to the toolbox it is in and the restrictions on the caller. - **Activity search** (Search). Search for activities. Results are returned ordered by date descending. Examples: * To list activities on a lead, use the lead_ids filter. * To list conversations, filter for calls and meetings. * Filter for Email to get individual messages, or EmailThread to get one result… - **Aggregation** (Action). Perform an aggregation to answer questions like: * How many emails were sent this week? * Calls by user this week (Who made the most?) You MUST first fetch the list of available fields using the `get_fields` tool. - **Close product knowledge search** (Search). Search Close product documentation and knowledge base for relevant information. Use this tool when users ask about: * How to use specific Close features * Close API documentation and integration * Workflow automation and best practices * Product capabilities and limitations *… - **Customized builtin labels** (Action). Return the customized builtin labels. Only renamed labels are returned - an empty result means the default names apply. - **Fetch** (Action). Retrieve the contents of an arbitrary object by its ID. Currently supported are leads and contacts. - **Fetch call** (Action). Fetch a single call activity by ID. Returns the call's direction, outcome, participants, and (if available) its transcript. - **Fetch call task** (Action). Fetch a single call task by ID. - **Fetch comment** (Action). Fetch a single comment by ID. Returns the comment's rich-text (HTML) body, the thread and lead it belongs to, its @-mentions, and the resolved author and last-editor names. - **Fetch contact** (Action). Fetch an existing contact by ID. Returns the contact's details including name, title, email addresses, phone numbers, and URLs. - **Fetch custom activity instance** (Action). Fetch an existing custom activity instance by ID. A custom activity instance is an activity of a custom activity type, holding the custom field values defined by that type. Returns the full instance, including its custom field values and the resolved lead, contact, and user… - **Fetch custom object instance** (Action). Fetch an existing custom object instance by ID. A custom object instance is a record of a custom object type, attached to a lead and holding the custom field values defined by that type. Returns the full instance, including its custom field values and the resolved lead, custom… - **Fetch custom object type** (Action). Fetch a single custom object type by its ID. A custom object type defines the shape of a category of custom objects, including the custom fields its instances hold. Returns the type with its custom fields. - **Fetch email** (Action). Fetch a single email activity by ID. - **Fetch email template** (Action). Fetch an email template by ID. Returns the complete email template with all its details. - **Fetch email thread** (Action). Fetch a single Email Thread by ID. Returns thread metadata plus its most recent emails, newest first, with plaintext bodies. Returns only IDs for older messages. - **Fetch invoice** (Action). Fetch one of the organization's billing invoices by id. - **Fetch lead** (Action). Fetch an existing lead (company) by ID. - **Fetch lead smart view** (Action). Fetch a lead smart view (saved search) by ID. - **Fetch lead status** (Action). Fetch a lead status by ID. - **Fetch meeting transcript** (Action). Fetch a meeting's Notetaker transcript(s) by meeting activity ID. Returns the meeting's speaker breakdown, summary, and full speaker-labeled transcript text. Only covers Notetaker (meeting) transcripts; call transcripts are served by `fetch_call`. - **Fetch membership** (Action). Fetch one of the organization's members by user id. - **Fetch note** (Action). Fetch an existing note by ID. Returns the full note details including title, text, and metadata. - **Fetch opportunity** (Action). Fetch a specific opportunity by ID. Returns the complete opportunity with all its details. - **Fetch opportunity status** (Action). Fetch an opportunity status by ID. - **Fetch pipeline and opportunity statuses** (Action). Fetch an opportunity pipeline, including its opportunity statuses, by ID. - **Fetch role** (Action). Fetch one of the organization's roles by id, with every permission it grants. Use `list_roles` to resolve a role name to its id. - **Fetch sms** (Action). Fetch a single SMS activity by ID. Returns the complete SMS, including message text and attachments. - **Fetch sms template** (Action). Fetch an SMS template by ID. Returns the complete SMS template with all its details. - **Fetch task** (Action). Fetch an existing task by ID. Returns the task's details including the associated lead, contact, assignee, due date, priority, and completion status. - **Fetch workflow** (Action). Fetch a single workflow by ID. - **Find agent configs** (Action). List all voice agents configured for the organization. Voice agents are AI callers that place outbound calls to leads' contacts on the user's behalf. Returns each voice agent's ID and name. Use this to find the right voice agent ID when scheduling a call or assigning a call… - **Find call outcomes** (Action). List currently configured call outcomes and their descriptions. Omit agent_config_id for all organization call outcomes. Supply it for a voice agent's available outcomes; agents without a conversation type use all organization call outcomes. Requires ViewVoiceAgents when… - **Find call tasks** (Action). Find call tasks based on various filters. You can filter by lead, contact, assignee (a user or a voice agent), completion state, and scheduled/created/updated dates. - **Find contact custom fields** (Action). List all contact custom fields defined for the organization. Includes both contact-specific fields and shared fields associated with contacts. Returns each field's ID, name, description, type, allowed choices (for choice fields), whether multiple values are accepted, and… - **Find custom activities** (Action). List all active (non-archived) Custom Activity Types in the organization, along with the custom fields defined on each type. Call this before creating a workflow with a "custom-activity-event" trigger so you can look up the correct Custom Activity Type ID. - **Find custom activity instances** (Action). Find a lead's custom activity instances based on various filters. A custom activity instance is an activity of a custom activity type, holding the custom field values defined by that type. Always scoped to a single lead; optionally filter by attributed user, one or more custom… - **Find custom object instances** (Action). Find a lead's custom object instances. A custom object instance is a record of a custom object type, attached to a lead and holding the custom field values defined by that type. Always scoped to a single lead; optionally filter to a single custom object type. Results are… - **Find custom object types** (Action). List all custom object types in the organization, along with the custom fields defined on each type. - **Find email templates** (Action). List or find email templates - **Find forms** (Action). List all web forms in the organization. Call this before creating a workflow with a "form-submission-event" trigger so you can look up the correct Form ID. - **Find groups** (Action). List all groups in the organization. - **Find invoices** (Action). Find the organization's billing invoices, newest first. Invoices without a date sort first. - **Find lead custom fields** (Action). List all lead custom fields defined for the organization. Returns each field's ID, name, description, type, allowed choices (for choice fields), whether multiple values are accepted, and whether it is a shared field. Useful for deciding which custom field to read or write when… - **Find lead smart views** (Action). List lead smart views (saved searches). - **Find lead statuses** (Action). List or find lead statuses for the organization - **Find meeting outcomes** (Action). List all outcomes applicable to meetings available in the organization. - **Find memberships** (Action). List the organization's members with each member's role name, whether the role is built-in or custom, active/inactive status, and join date. Richer than `org_users` — prefer this unless you only need a name or email. Most recent members first. - **Find notes** (Action). Find notes based on various filters. - **Find opportunities** (Action). Find opportunities by status (active/won/lost), owner, lead, or close-date range, optionally only those needing attention, sorted by soonest close, largest value, or highest confidence. Returns each opportunity with resolved lead, contact, owner, and status names;… - **Find opportunity custom fields** (Action). List all opportunity custom fields defined for the organization. Includes both opportunity-specific fields and shared fields associated with opportunities. Returns each field's ID, name, description, type, allowed choices (for choice fields), whether multiple values are… - ...and 71 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.