The iClosed Model Context Protocol (MCP) server lets AI assistants such as Claude, Cursor and VS Code work with your iClosed workspace in plain language. Your assistant can look up contacts, notes, deals, events and calls, book or reschedule calls, and record changes.
Beta
The iClosed MCP server is in beta. Tools and behavior may change before general availability.
MCP server URL: https://mcp.iclosed.io/mcp
- Turn on MCP. An account owner or super admin opens Settings → Developer → MCP and turns on Allow AI assistants (MCP) to connect to this workspace. The account owner and super admins can connect without this step.
- Add the URL to your assistant. Paste
https://mcp.iclosed.io/mcpinto your assistant's MCP or connector settings. - Sign in and allow. Your assistant opens iClosed in the browser. Sign in, review the permissions, and click Allow access.
Step-by-step guides: Claude · Claude Code · Cursor · VS Code · Other clients
You need:
- An iClosed account on any plan.
- MCP turned on for your workspace. An account owner or super admin turns it on in Settings → Developer → MCP. It is off by default for members; the account owner and super admins can always connect. See For admins.
- An MCP-compatible assistant that can connect to a remote server over HTTPS and sign in with OAuth.
You don't need an API key. Leave any "headers" or "API key" fields in your assistant empty.
- MCP is an open standard for connecting AI assistants to tools and data. The iClosed MCP server exposes workspace actions as tools that your assistant can call. Each tool maps to an operation in the public API.
- You sign in with OAuth 2.1 and PKCE, the authorization method MCP clients expect. Your assistant registers itself with iClosed automatically, then you approve the requested permissions on the iClosed consent screen.
- Access follows your role. The assistant acts as you, in the workspace you approved. It can only do what your iClosed role allows, even if it requested more.
- Rate limits: each connection can make up to 20 requests per 10 seconds. Every request to the MCP server counts, not only tool calls. The standard per-endpoint API rate limits also apply. If you go over the limit, the server responds with
429 Too Many Requestsand aRetry-Afterheader. - Transport: Streamable HTTP.
| Area | What the assistant can do |
|---|---|
| Contacts | List, search, view, create and update contacts; view a contact's journey |
| Contact notes | Read and add notes on a contact |
| Custom fields | Read fields and contact stages; create and update fields; set field answers |
| Deals | List, create and update deals |
| Events | List events, check available booking slots, activate or deactivate an event |
| Event calls | Search calls, book, reschedule or cancel a call, reassign the closer |
| Call outcomes | Set a call's outcome, with notes, and create the deal when it's won |
| Products | List, create and update products |
| Transactions | List, record, update and delete transactions |
| Users and availability | List workspace users and their availability schedules |
Tool names are the same in every client, though clients display them differently. See Tools for the full list.
- Security and permissions — scopes, consent and data handling.
- Troubleshooting and FAQ
- OAuth Clients — for developers building their own OAuth app (not needed for MCP).
- API Reference — the REST operations the MCP tools call.