> ## Documentation Index > Fetch the complete documentation index at: https://docs.caylex.ai/llms.txt > Use this file to discover all available pages before exploring further. # Close > Automate workflows with Close.iO and Minecraft PE The Close MCP Server connects AI agents to Close data, enabling seamless workflow automation, real-time content management, and integration with platforms like Cursor and Claude for enhanced decision-making and operational efficiency. ## Server Details | Property | Value | | -------------- | -------------------------- | | **Transport** | Streamable HTTP | | **Hosting** | Remote (externally hosted) | | **Categories** | CRM, Business Operations | ## Authentication This server supports the following authentication method: ### OAuth **Scopes:** `mcp.read,`, `mcp.write` During the server onboarding flow, you will be prompted to complete the OAuth flow to grant access. See the [Close Authentication guide](/oauth-guides/close) for step-by-step credential configuration. ## Getting Started Navigate to the **Server Library** and click on the **New Server** button. Find **Close** in the Caylex Catalog. Go through the server onboarding flow. Add the server to a [project](https://app.caylex.dev/projects) by configuring project connections. Its tools are now available to any agents connected to that project. ## Available Tools This server provides **63** tools: Fetch an SMS template by ID. Returns the complete SMS template with all its details. Fetch an opportunity pipeline, including its opportunity statuses, by ID. Create a new opportunity pipeline. Use the create\_opportunity\_status tool to add statuses to the pipeline. Update an existing opportunity pipeline. Only fields that are provided will be updated. Permanently delete an opportunity pipeline. A pipeline can only be deleted if it has no statuses. The last pipeline cannot be deleted. Fetch an opportunity status by ID. Create a new opportunity status. Update the label of an existing opportunity status. Return general information about the organization and the user. Return active users (memberships) which are part of the current org. List or find lead statuses for the organization Fetch a lead status by ID. Create a new lead status. Update the label of an existing 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. List or find email templates Fetch an email template by ID. Returns the complete email template with all its details. 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 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. Permanently delete an email template. If the template is used in any workflows (sequences), it cannot be deleted. List or find SMS templates 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 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. Permanently delete an SMS template. If the template is used in any workflows (sequences), it cannot be deleted. 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 an existing lead (company). Only fields that are provided and not None will be updated. Fetch an existing lead (company) by ID. 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. Add a new address to an existing lead (company). Delete an address from an existing lead (company) if there is an exact match. List lead smart views (saved searches). Fetch a lead smart view (saved search) by ID. Update a lead smart view (saved search). Only fields that are provided and not None will be updated. Permanently delete a lead smart view (saved search). Create a new contact for a lead. A contact represents a person associated with a lead (company). Fetch an existing contact by ID. Returns the contact's details including name, title, email addresses, phone numbers, and URLs. 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. 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. 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 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 for activities. Results are returned ordered by date descending. Examples: 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: 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. Retrieve the contents of an arbitrary object by its ID. Currently supported are leads and contacts. Perform an aggregation to answer questions like: You MUST first fetch the list of available leads of fields using the `get_fields` tool. Use this field ONLY to get a list of fields for the aggregation tool. Search Close product documentation and knowledge base for relevant information. Use this tool when users ask about: Example queries: List or find workflows Create a new workflow (a.k.a. sequence) with Draft status. List all opportunity pipelines and their opportunity statuses in the organization. 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 based on various filters. You can filter by lead, user, status, dates, and more. Fetch a specific opportunity by ID. Returns the complete opportunity with all its details. 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 an existing opportunity. Only fields that are provided will be updated. The value should be specified in cents (e.g., \$100.00 = 10000). Permanently delete an opportunity. This action cannot be undone. All data associated with the opportunity will be removed. 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 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. 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. 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. 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. List all outcomes applicable to calls available in the organization. List all outcomes applicable to meetings available in the organization. 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. ## Related Servers ## References