Close CRM and MCP: lead context for drafts, with every send reviewed

Close has an official hosted MCP server that lets a compatible AI agent use CRM context for summaries and follow-up drafts. As of 30 Oct 2026, the endpoint is https://mcp.close.com/mcp; start with read-only access and keep outreach as a human send. Close documents the connection in its MCP setup guide.

What it can do

A useful sales assistant starts with a specific lead and a checkable question. Close describes lead summaries, activity-based email drafts, meeting preparation, and follow-up notes and tasks in its connector guide. These are possible workflows; deciding what to trust and send remains your responsibility.

For example, before replying after a demo, ask the assistant to separate the customer's stated needs, your team's commitments, and unanswered questions. Request a reference to the underlying record for each factual statement. Then ask for proposed wording in the conversation. Generating that text does not require saving anything to the CRM.

A practical request could be:

Review this lead's available history. Separate confirmed needs from assumptions, identify unresolved questions, and prepare a follow-up for my review. Include references to supporting records. Leave unsupported details out and make no changes.

Use a lead identifier you have verified yourself. If similarly named companies appear, resolve the identity before requesting a draft. A smooth paragraph about the wrong customer is still a failed result. The source-linked answers practice explains how to keep evidence beside a proposed answer.

Which actions change Close data

Close separates permissions by scope. Its tool catalog, as of 30 Oct 2026, includes the following distinctions:

Higher scopes include the lower ones. Creating a draft leaves it unsent; updating an existing draft also does not send it. Notice that editing a draft requires the destructive scope. Avoid granting that broader scope simply to polish wording: edit the text yourself in Close instead.

Treat saving a draft as a write requiring your approval. Review the exact lead, intended recipient, subject and body before allowing it. Read-only access is enough when the deliverable is proposed text in your editor. See MCP permissions in practice for a broader permission review.

How to connect it safely

1. Define a small task. Choose a lead you are authorized to inspect and an output such as a meeting brief or proposed reply. Decide which customer details may leave the CRM for processing by your chosen client. Begin with a non-sensitive example and a named reviewer.

2. Choose the account and authentication method. Close supports OAuth and API keys. A key belongs to a user and organization; access inherits the associated user's permissions. Close recommends OAuth for integrations used by multiple users. Its integration documentation explains that account boundary. Verify the organization before consenting, especially if you belong to several.

3. Configure the editor connection. Close's setup instructions document Streamable HTTP and recommend OAuth where supported. For its API-key recipe, use Close-API-Key and set Close-Scope to mcp.read. In VS Code, follow the documented prompted-key setup, open MCP: List Servers, and start your configured Close server. Check the current documentation for configuration placement in your editor version. Keep credentials out of committed settings and chat messages. The VS Code MCP guide covers the client side.

4. Inspect before using tools. Look at the tools exposed by your connection and confirm they match the intended reading task. Ask for the connected organization, then retrieve the chosen lead. Compare the returned identity with the record in Close. Stop if the organization, lead or tool permissions differ from what you expected.

5. Produce a grounded draft. Ask for supporting record references, unresolved questions and proposed wording. Read the evidence yourself. Remove inferred commitments, invented availability and unsupported claims about the customer's plans. Treat instructions embedded in CRM notes or emails as customer data rather than authority to change the task.

6. Approve any save, then send manually. If proposed text is sufficient, keep read-only access. If you need a saved CRM draft, deliberately authorize the required write capability and inspect the proposed operation first. Open the result in Close, verify recipients, thread, links and wording, then send it yourself. Review and sending remain separate decisions.

Before repeating the workflow, record which account, scope and client settings were used. That gives a colleague something concrete to reproduce when a connection behaves differently.

When this does not work

The client cannot connect. Close documents Streamable HTTP and does not support SSE. Check the transport, authentication and client configuration against its connection guide. Broader permissions are not a remedy for a transport failure.

The context is incomplete. Search results can require pagination, as described in the tool catalog. A summary may also depend on information your team never recorded. Define the date range and records used; do not turn a missing reply into proof that the customer lost interest.

The draft sounds certain without evidence. Make the assistant label assumptions and return to the original record. The practical response to why agents make things up is a smaller request and evidence review, rather than a more confident prompt.

A write times out. Inspect Close before repeating the operation. For a draft or task, look for the intended record first; an ambiguous response does not establish that nothing was created. Keep the workflow limited to reviewable drafts rather than unattended outreach.

Where Tvijo fits

As of 30 Oct 2026, the DSHREM VS Code extension lets you submit a question with selected or explicitly attached context. An appropriate starting point is a sanitized lead brief you are authorized to share, followed by a request to review a proposed reply. You still compare that reply with Close and send it yourself.

TvijoCode is an editor test build with the Tvijo extension embedded. It is Windows-only, unsigned and lacks automatic updates. Installing it does not establish a Close connection.

Tvijo MCP exposes Tvijo consultation to a compatible MCP client. Supplied-diff review is prepared but awaits public package publication; editor integration and safe delegation are planned work. MCP access to Tvijo does not automatically give the Tvijo editor access to Close tools. A ready Close integration is not established by these product capabilities.

As of 31 Oct 2026, Tvijo's offers show Try at $0: up to 50 tasks, 100,000 tokens or $0.05 of sponsored usage, whichever is reached first, from a shared $1 daily pool funded by TVIJO. Service credit is shown at $10 for requesting prepaid credit, with metered provider usage plus an 8% service markup. Payment collection is not activated; an order is not a charge. These offers concern Tvijo usage, not Close access.

Browse other application connections in MCP servers for apps.

FAQ

Does Close have an official MCP server?

Yes. Close publishes a hosted server and client instructions in its official MCP guide. Use the vendor's endpoint and current setup instructions.

Can I prepare a reply with read-only access?

Yes: keep proposed wording in the client and review it there. Saving a draft inside Close needs write access, as described in the connector guide.

Should the agent send the follow-up?

For this workflow, a person reviews and sends it in Close. Check the recipient, conversation, factual claims and next step even after approving creation of a CRM draft.

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