> For a complete page index, fetch https://developer.close.com/llms.txt # Close MCP Tools The Close MCP Server provides tools organized by scope. Each higher scope includes all tools from the lower scopes. ## Read-only Tools – `mcp.read` Read-only tools for searching, fetching, and exploring your Close data. ### Activity Search – `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. ### Aggregate Objects – `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. ### Close Product Knowledge Search – `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" ### Fetch Object – `fetch` > Retrieve the contents of an arbitrary object by its ID. > Currently supported are leads and contacts. ### Fetch Contact – `fetch_contact` > Fetch an existing contact by ID. > Returns the contact's details including name, title, email addresses, phone numbers, and URLs. ### Fetch Email Template – `fetch_email_template` > Fetch an email template by ID. > Returns the complete email template with all its details. ### Fetch Lead – `fetch_lead` > Fetch an existing lead (company) by ID. ### Fetch Lead Smart View – `fetch_lead_smart_view` > Fetch a lead smart view (saved search) by ID. ### Fetch Lead Status – `fetch_lead_status` > Fetch a lead status by ID. ### Fetch Opportunity – `fetch_opportunity` > Fetch a specific opportunity by ID. > Returns the complete opportunity with all its details. ### Fetch Opportunity Status – `fetch_opportunity_status` > Fetch an opportunity status by ID. ### Fetch Pipeline – `fetch_pipeline_and_opportunity_statuses` > Fetch an opportunity pipeline, including its opportunity statuses, by ID. ### Fetch SMS Template – `fetch_sms_template` > Fetch an SMS template by ID. > Returns the complete SMS template with all its details. ### Find Agent Configs – `find_agent_configs` > List all AI agent configurations (also known as "Chloe", bots, or AI agents) > defined for the organization. > Returns each agent's ID and name. Use this to find the right > agent ID when assigning a call step to an AI agent in a workflow. > Users may refer to agents as "agents", "bots", "Chloe", or by their configured > name. When more than one agent exists, pick the most appropriate one based on > the name. ### Find Call Outcomes – `find_call_outcomes` > List all outcomes applicable to calls available in the organization. ### Find Custom Activity Types – `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. ### Find Email Templates – `find_email_templates` > List or find email templates ### Find Web Forms – `find_forms` > 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 – `find_groups` > List all groups in the organization. ### List Lead Custom Fields – `find_lead_custom_fields` > 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 working with leads. ### Find Lead Smart Views – `find_lead_smart_views` > List lead smart views (saved searches). ### Find Lead Statuses – `find_lead_statuses` > List or find lead statuses for the organization ### Find Meeting Outcomes – `find_meeting_outcomes` > List all outcomes applicable to meetings available in the organization. ### Find Opportunities – `find_opportunities` > Find opportunities based on various filters. > You can filter by lead, user, status, dates, and more. ### Find Pipelines – `find_pipelines_and_opportunity_statuses` > List all opportunity pipelines and their opportunity statuses in the organization. ### Find Scheduling Links – `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. ### Find SMS Templates – `find_sms_templates` > List or find SMS templates ### Find Workflows – `find_workflows` > List or find workflows ### Get Fields – `get_fields` > Use this field ONLY to get a list of fields for the aggregation tool. ### Lead Search – `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. ### Org Info – `org_info` > Return general information about the organization and the user. ### Org Users – `org_users` > Return active users (memberships) which are part of the current org. ### Paginate Search Results – `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. ### Search Objects – `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. ## Write (Safe) Tools – `mcp.write_safe` Includes all `mcp.read` scoped tools, plus these tools for creating and updating data: ### Create Address – `create_address` > Add a new address to an existing lead (company). ### Create Contact – `create_contact` > Create a new contact for a lead. > A contact represents a person associated with a lead (company). ### Create Email Template – `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. ### Create Lead – `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. ### Create Lead Status – `create_lead_status` > Create a new lead status. ### Create Opportunity – `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). ### Create Opportunity Status – `create_opportunity_status_tool` > Create a new opportunity status. ### Create Pipeline – `create_pipeline` > Create a new opportunity pipeline. > Use the create\_opportunity\_status tool to add statuses to the pipeline. ### Create SMS Template – `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. ### Create Task – `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. ### Create Workflow – `create_workflow` > Create a new workflow (a.k.a. sequence) with Draft status. ## Write (Destructive) Tools – `mcp.write_destructive` Includes all `mcp.read` and `mcp.write_safe` scoped tools, plus these tools for updating and deleting data: ### Delete Address – `delete_address` > Delete an address from an existing lead (company) if there is an exact > match. ### Delete Contact – `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. Activities on the lead are not > affected. > This action cannot be undone. > ONLY call this if the user specifically instructed you to delete the contact. ### Delete Email Template – `delete_email_template` > Permanently delete an email template. > If the template is used in any workflows (sequences), it cannot be deleted. ### Delete Lead – `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. ### Delete Lead Smart View – `delete_lead_smart_view` > Permanently delete a lead smart view (saved search). ### Delete 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. ### Delete Opportunity – `delete_opportunity` > Permanently delete an opportunity. > This action cannot be undone. All data associated with the opportunity will be removed. ### Delete 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. ### Delete Pipeline – `delete_pipeline` > Permanently delete an opportunity pipeline. > A pipeline can only be deleted if it has no statuses. The last pipeline > cannot be deleted. ### Delete SMS Template – `delete_sms_template` > Permanently delete an SMS template. > If the template is used in any workflows (sequences), it cannot be deleted. ### Update Contact – `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. ### Update Email Template – `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. ### Update Lead – `update_lead` > Update an existing lead (company). > Only fields that are provided and not None will be updated. ### Update Lead Smart View – `update_lead_smart_view` > Update a lead smart view (saved search). > Only fields that are provided and not None will be updated. ### Update Lead Status – `update_lead_status` > Update the label of an existing lead status. ### Update Opportunity – `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). ### Update Opportunity Status – `update_opportunity_status_tool` > Update the label of an existing opportunity status. ### Update Pipeline – `update_pipeline` > Update an existing opportunity pipeline. > Only fields that are provided will be updated. ### Update SMS Template – `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.