Connect Close to Andromity with the Close MCP server

Close hosts an official MCP server at https://mcp.close.com/mcp. With it, Andromity can look up the lead behind a request, read its activity history and opportunities, and add a note or task when you finish the related work.

Close recommends OAuth 2.0 with dynamic client registration, so connecting is a single browser sign-in.

What the agent can do with Close

• Search leads and contacts, by natural language or by keyword, status or smart view (search, lead_search).
• Search activities such as calls, emails and meetings (activity_search).
• Answer counting and grouping questions across objects (aggregation, get_fields).
• Fetch leads, contacts, opportunities, notes, tasks, emails and call records by ID (fetch_lead, fetch_opportunity, fetch_note).
• Create leads, contacts, notes, comments, tasks and opportunities (create_lead, create_note, create_task, create_opportunity).
• Save an unsent draft email for a person to review (create_draft_email).
• With the widest scope, update, merge and delete records (update_lead, merge_leads, delete_lead).

Example prompts

Ask for the work in plain language. Naming the server helps, for example “use the Close MCP server”.

• Find the Close lead for acme.com and summarize its recent calls and emails, then check whether the bug described in them is covered by a test in this repo.
• Use Close to count opportunities by status so I can verify the numbers my reporting query in src/reports returns.
• Create a Close task on the Acme lead to tell them the export fix shipped, and add a note with the commit summary.
• List the custom fields on Close leads and check that our CRM sync module maps all of them.

Connect Close

1. In VS Code, open Andromity Hub → MCP Servers → Discover. In the terminal app, open /settings → MCP → + Connect an app. Find Close and select Connect.
2. Sign in to Close in your browser and approve the connection.
3. Andromity saves Close to ~/.andromity/mcp.json and connects it. If you cancel sign-in, nothing is saved.

See Connect an app for how Andromity stores connectors and tokens.

Access and safety

• Close scopes the server with the Close-Scope header: mcp.read is read-only, mcp.write_safe reads and writes data, and mcp.write_destructive also deletes data in the organization. The scope decides which tools are available.
• To pin a scope, add the server by hand in mcp.json with the Close-Scope header and sign in from its card. Close also documents an API-key option with the Close-API-Key header for clients that send custom headers.
• Andromity's permission modes apply to every Close tool call. In TRUST mode, tools with create, update or delete in the name ask first.

In an untrusted folder, MCP servers don’t start at all. Read workspace trust and permission modes for the full model.

Limits to know

• Close does not support SSE on this server. Use the Streamable HTTP endpoint.
• Close's documentation does not state rate limits for the MCP server.
• Delete tools are permanent, and merge_leads deletes the source lead.

Questions

Does Close have an official MCP server?

Yes. Close hosts a remote MCP server at https://mcp.close.com/mcp with OAuth 2.0 and dynamic client registration.

Can I give the agent read-only access to Close?

Yes. Close's mcp.read scope exposes only read tools. Add the server by hand in mcp.json with a Close-Scope header of mcp.read.

Can the agent delete Close records?

Only with the mcp.write_destructive scope. Lower scopes do not include delete tools.

Sources

This guide is based on Close’s own documentation. The app controls its server, so tools can change; check the source for the current list.

• Close MCP Server
• Close MCP tools by scope

Close is a trademark of its owner. Andromity is not affiliated with or endorsed by Close.