# Close

> Manage leads, contacts, opportunities, and tasks in Close from an AI agent — official scoped MCP.

[Canonical HTML page](https://top-mcps.com/mcp/close-crm) · [server.json](https://top-mcps.com/mcp/close-crm.json) · [methodology](https://top-mcps.com/about/methodology)

## At a glance

- **Maintainer:** Close
- **Transport:** Streamable HTTP
- **Auth model:** OAuth 2.1
- **Required secrets:** None
- **Supported clients:** Claude, Cursor, ChatGPT, n8n, Any MCP-compatible client
- **Latest version:** latest
- **Last verified:** 2026-07-16
- **Score:** 57/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Homepage:** https://help.close.com/docs/mcp-server

## Quick answer

**What it does.** Exposes Close CRM objects as MCP tools — leads, contacts, opportunities, and tasks — over a remote HTTP server, with three explicit permission scopes.

**Best for:**
- Reading and updating Close leads + opportunities
- Scoped access (read / write-safe / destructive)
- Task and follow-up creation
- Inside-sales pipeline automation
- OAuth 2.0 DCR with no pasted key

**Not for:**
- Non-Close CRM stacks
- Self-hosted-only requirements
- Teams without a Close subscription

## Description

Close's official MCP is a remote server at mcp.close.com with a clean permission model: the Close-Scope header selects mcp.read (read-only), mcp.write_safe (read + write), or mcp.write_destructive (read + write + delete). Connect over OAuth 2.0 (Dynamic Client Registration) and an agent can work leads, contacts, opportunities, and tasks in a sales-first CRM.

## Why it matters

Close is the CRM inside-sales teams live in, and its scoped MCP is a model of least-privilege design: you can give an agent read-only pipeline access without any ability to mutate or delete.

## Key features

- Official remote MCP at mcp.close.com/mcp
- Three scopes: read, write_safe, write_destructive
- Leads, contacts, opportunities, tasks
- OAuth 2.0 Dynamic Client Registration
- HTTP streamable transport

## FAQ

### How do I keep it read-only?

Set the Close-Scope header to `mcp.read`. Use `mcp.write_safe` to allow creates and updates, and `mcp.write_destructive` only when deletes are intended.

### How does it authenticate?

OAuth 2.0 with Dynamic Client Registration (DCR) is recommended; an API-key header is also supported for scripted setups.

### Which objects can it touch?

Leads, contacts, opportunities, and tasks — the core Close CRM objects — bounded by the scope you grant.

## Changelog

- **2026-07-16** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-06-01** — Initial directory listing.