Labsco
MCP SERVER · OFFICIAL PROJECT

Close MCP Server

by Close ↗

Leads, contacts, deals, tasks and emails in Close, searched and updated by your agent, with reports on your pipeline.

CRM & Sales Pipeline✓ Popular vendor Official
Needed to connect
An account, signed in with OAuth
Tools
121 · from the project's docs
Setup effort
Paste a URL, then authorize
Source
Popular vendor Official

Close records changed directly, with deletion kept behind its own scope.

Reps can turn a call into CRM work in one pass, with the Notetaker transcript becoming a note, a follow-up task and a drafted email, and managers can total the pipeline by asking.

What it is

A remote MCP server Close runs at mcp.close.com/mcp. It connects to one Close organization at a time, and what it may do depends on the scope you grant: read only, read and write, or read, write and delete.

What you get

  • Leads and contacts found with a plain-language search, and activities such as calls, emails and notes searched by date
  • Counts and totals across your data, for questions like how many deals closed this month
  • Leads, contacts, opportunities, tasks, notes and comments created and updated
  • Draft emails written on a lead, and email and SMS templates managed
  • Pipelines, lead statuses, saved searches and workflows (sequences) set up
  • Meeting transcripts from Close's Notetaker read back
  • Voice agents reviewed, their calls scheduled, and changes proposed before they are applied
  • With the delete scope: leads, contacts, deals, tasks and other records permanently deleted

Requirements

A Close account. Sign in with OAuth and pick the organization and scope, which Close recommends, or send a Close API key with a scope header. In Claude's web and desktop apps the Close connector needs a paid Claude plan; the Claude desktop app also connects on the free plan. Start with read or read-and-write scope; the delete scope lets it permanently remove leads and other records. Each Close organization needs its own connection.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen