Close
Manage leads, contacts, and deals in Close CRM.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Org Info: Return general information about the organization and the user.
- Org Users: Return active users (memberships) which are part of the current org.
- Find Lead Statuses: List or find lead statuses for the organization
What data it sees
Do you need an account
No: the server works without sign-in
Manage leads, contacts, and deals in Close CRM. Log calls, send emails, create tasks, and track pipeline activity.
How to connect
How to connect Close to Claude
The server address to paste into Claude settings:
https://close.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Close to ChatGPT
The server address to paste into ChatGPT settings:
https://close.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Close to Cursor
The server address to paste into Cursor settings:
https://close.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (60)
Raw names from tools/list. Only developers need these.
| org_info | Return general information about the organization and the user. |
| org_users | Return active users (memberships) which are part of the current org. |
| find_lead_statuses | List or find lead statuses for the organization |
| fetch_lead_status | Fetch a lead status by ID. |
| create_lead_status | Create a new lead status. |
| update_lead_status | Update the label of an existing lead status. |
| delete_lead_status | Permanently delete a lead status. Cannot delete if it's the last lead status in the organization or there are leads currently using this status. |
| find_email_templates | List or find email templates |
| fetch_email_template | Fetch an email template by ID. Returns the complete email template with all its details. |
| update_email_template | Update an existing email template. Only fields that are provided and not None will be updated. Handling of attachments and unsubscribe links via this tool is currently unsupported. Email template body should be HTML formatted. Use template tags as placeholders, for example: {{ organization.name }} to refer to the sender's organization name. {{ user.first_name }} {{ user.last_name }} {{ user.email }} {{ user.phone }} to refer to the user sending the email. {{ lead.display_name }} to refer to the lead name (recipient's name/company). {{ contact.first_name }} {{ contact.last_name }} to refer to the recipient. |
| create_email_template | Create a new email template. Handling of attachments and unsubscribe links via this tool is currently unsupported. Email template body should be HTML formatted. Use template tags as placeholders, for example: {{ organization.name }} to refer to the sender's organization name. {{ user.first_name }} {{ user.last_name }} {{ user.email }} {{ user.phone }} to refer to the user sending the email. {{ lead.display_name }} to refer to the lead name (recipient's name/company). {{ contact.first_name }} {{ contact.last_name }} to refer to the recipient. |
| delete_email_template | Permanently delete an email template. If the template is used in any workflows (sequences), it cannot be deleted. |
| find_sms_templates | List or find SMS templates |
| fetch_sms_template | Fetch an SMS template by ID. Returns the complete SMS template with all its details. |
| update_sms_template | Update an existing SMS template. Only fields that are provided will be updated. Fields that are not provided will remain unchanged. Handling of attachments via this tool is currently unsupported. Use template tags as placeholders, for example: {{ organization.name }} to refer to the sender's organization name. {{ user.first_name }} {{ user.last_name }} {{ user.email }} {{ user.phone }} to refer to the user sending the message. {{ lead.display_name }} to refer to the lead name (recipient's name/company). {{ contact.first_name }} {{ contact.last_name }} to refer to the recipient. |
| create_sms_template | Create a new SMS template. Handling of attachments via this tool is currently unsupported. Use template tags as placeholders, for example: {{ organization.name }} to refer to the sender's organization name. {{ user.first_name }} {{ user.last_name }} {{ user.email }} {{ user.phone }} to refer to the user sending the message. {{ lead.display_name }} to refer to the lead name (recipient's name/company). {{ contact.first_name }} {{ contact.last_name }} to refer to the recipient. |
| delete_sms_template | Permanently delete an SMS template. If the template is used in any workflows (sequences), it cannot be deleted. |
| create_lead | Create a new lead (company). After creating a lead, you should usually add an address or contact (including phone or email) to the lead. |
| update_lead | Update an existing lead (company). Only fields that are provided and not None will be updated. |
| fetch_lead | Fetch an existing lead (company) by ID. |
| delete_lead | Permanently delete an existing lead (company) by ID including all of its addresses, contacts, opportunities, tasks, and activities. ONLY call this if the user specifically instructed you to delete the lead, and you confirmed what the deletion will entail and that it cannot be reversed. |
| create_address | Add a new address to an existing lead (company). |
| delete_address | Delete an address from an existing lead (company) if there is an exact match. |
| find_lead_smart_views | List lead smart views (saved searches). |
| fetch_lead_smart_view | Fetch a lead smart view (saved search) by ID. |
| update_lead_smart_view | Update a lead smart view (saved search). Only fields that are provided and not None will be updated. |
| delete_lead_smart_view | Permanently delete a lead smart view (saved search). |
| create_contact | Create a new contact for a lead. A contact represents a person associated with a lead (company). |
| fetch_contact | Fetch an existing contact by ID. Returns the contact's details including name, title, email addresses, phone numbers, and URLs. |
| update_contact | Update an existing contact. You can update a contact's name, title, email addresses, phone numbers, and URLs. Only fields that are provided will be updated. |
| delete_contact | Permanently delete an existing contact. This will remove the contact from its lead including its email addresses, phone numbers, and URLs will be removed. Activitise on the lead are not affected. This action cannot be undone. ONLY call this if the user specifically instructed you to delete the contact. |
| lead_search | Perform a simple lead search and return the initial set of results. Use this to retrieve all leads, most recent leads, search leads by keyword, or filter by lead status and smart view. For more complex searches use the `search` tool instead. Leads will be returned by last updated first. |
| paginate_search | Paginate an existing search (from search or lead_search) to retrieve more results. Use the search_id from a previous search and a pagination cursor. |
| activity_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. |
| search | Perform a natural language search for leads or contacts. If a more specific search tool (like lead_search or activity_search) satisfies the request, use that tool instead. You can reference related objects like activities (such as calls, emails, meetings, notes, custom activities, etc.), opportunities, tasks as long as they are part of a lead query. Example queries: - leads not contacted in the past week - leads assigned to me with uncompleted tasks - leads with an active opportunity over $500 - contacts with CTO title Each returned result will contain a title label, preview text, object ID, and URL. The initial set of results, total count of all results, and a URL to open the results in Close is returned. To retrieve more results, use the returned cursor and call the paginate_search tool using the cursor and search ID returned in this response. |
| fetch | Retrieve the contents of an arbitrary object by its ID. Currently supported are leads and contacts. |
| aggregation | 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 leads of fields using the `get_fields` tool. |
| get_fields | Use this field ONLY to get a list of fields for the aggregation tool. |
| close_product_knowledge_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 - Setup and configuration guidance Example queries: - "How do I set up automated lead assignment?" - "What are Close's API rate limits?" - "How to create custom fields in Close?" - "Best practices for email templates in Close" |
| find_workflows | List or find workflows |
| create_workflow | Create a new workflow (a.k.a. sequence) with Draft status. |
| find_pipelines_and_opportunity_statuses | List all opportunity pipelines and their opportunity statuses in the organization. |
| fetch_pipeline_and_opportunity_statuses | Fetch an opportunity pipeline, including its opportunity statuses, by ID. |
| create_pipeline | Create a new opportunity pipeline. Use the create_opportunity_status tool to add statuses to the pipeline. |
| update_pipeline | Update an existing opportunity pipeline. Only fields that are provided will be updated. |
| delete_pipeline | Permanently delete an opportunity pipeline. A pipeline can only be deleted if it has no statuses. The last pipeline cannot be deleted. |
| fetch_opportunity_status | Fetch an opportunity status by ID. |
| create_opportunity_status_tool | Create a new opportunity status. |
| update_opportunity_status_tool | Update the label of an existing opportunity status. |
| delete_opportunity_status_tool | Permanently delete an opportunity status. Cannot delete if it's the last opportunity status in the organization or there are opportunities currently using this status. |
| find_opportunities | Find opportunities based on various filters. You can filter by lead, user, status, dates, and more. |
| fetch_opportunity | Fetch a specific opportunity by ID. Returns the complete opportunity with all its details. |
| create_opportunity | Create a new opportunity. Requires a lead ID and status ID. Other fields are optional. The value should be specified in cents (e.g., $100.00 = 10000). |
| update_opportunity | Update an existing opportunity. Only fields that are provided will be updated. The value should be specified in cents (e.g., $100.00 = 10000). |
| delete_opportunity | Permanently delete an opportunity. This action cannot be undone. All data associated with the opportunity will be removed. |
| find_call_outcomes | List all outcomes applicable to calls available in the organization. |
| find_meeting_outcomes | List all outcomes applicable to meetings available in the organization. |
| find_scheduling_links | List available scheduling links for the user and org. User-owned personal links come with a URL. Shared links come with a special template tag. Each can be inserted into generated templates. |
| create_task | Create a new task for a lead. A task represents a to-do item that can be assigned to a user and optionally associated with a contact. |
| find_custom_activities | List all active (non-archived) Custom Activity Types in the organization. Call this before creating a workflow with a "custom-activity-event" trigger so you can look up the correct Custom Activity Type ID. |