Skip to content
Last updated

Connect iClosed to other clients

Any assistant or editor that supports remote MCP servers over Streamable HTTP with OAuth sign-in can connect to iClosed.

Before you connect: MCP must be turned on for your workspace (Settings → Developer → MCP, by an account owner or super admin). You don't need an API key. More about requirements.


Connection checklist

  1. Check that your client supports remote MCP. Look for "MCP", "connectors" or "remote server" in its settings or documentation.
  2. Add the server URL https://mcp.iclosed.io/mcp. Include the /mcp path. Leave headers and API key fields empty.
  3. Sign in when the client prompts you. Your browser opens the iClosed consent screen. Sign in and click Allow access.
  4. Reload the client if its documentation says MCP settings are cached.
  5. Check that it works: ask "Show me my contacts in iClosed."

The consent screens look the same in every client. See Connect iClosed to Claude for screenshots.


Clients that only support local (stdio) servers

Use mcp-remote as a bridge. It runs locally, connects to the iClosed server, and handles OAuth sign-in in your browser. It needs Node.js 18 or later.

Most clients accept a config like this:

{
  "mcpServers": {
    "iclosed": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.iclosed.io/mcp"]
    }
  }
}

If something goes wrong, see Troubleshooting.