I can't connect to Metricool MCP

Claude Desktop has a documented external bug that blocks the usual MCP connection path. Use mcp-remote instead.

1. In Claude Desktop, open Settings from your profile.

2. Go to Developer → Edit config under Local MCP servers.

3. Add this configuration:

   {
     "mcpServers": {
       "metricool-mcp": {
         "command": "npx",
         "args": [
           "-y",
           "mcp-remote",
           "https://ai.metricool.com/mcp"
         ]
       }
     }
   }

4. To authenticate with an API key instead of browser OAuth, use this config:

   {
     "mcpServers": {
       "metricool-mcp": {
         "command": "npx",
         "args": [
           "-y",
           "mcp-remote",
           "https://ai.metricool.com/mcp",
           "--header",
           "X-Mc-Auth: <METRICOOL_API_KEY>"
         ]
       }
     }
   }

5. Save the file and restart Claude Desktop.

6. If you used OAuth, complete browser authorization when prompted. If you used the API key method, the browser step is skipped.

7. In a chat, open Connectors and confirm Metricool is connected.

Full Claude Desktop and Claude Code steps: How to connect Metricool's MCP with Claude.

The endpoint, method, or authorization step is incomplete. Fix it in this order:

1. Confirm the server URL is exactly https://ai.metricool.com/mcp (no extra path, space, or alternate host).

2. Confirm your client is using the method from the table above. For example, N8N needs header auth, not a plain OAuth-only setup; Claude Desktop needs mcp-remote.

3. Complete the browser sign-in and choose Grant access when Metricool asks for permissions.

4. In Cursor, after install the server can appear unauthenticated until you click Connect and finish browser authorization.

5. In Gemini CLI, after adding the config, run /mcp auth metricool and finish browser authorization.

6. In Claude Code, run /mcp, select Metricool, then authenticate when prompted.

N8N connects with header token auth, not the URL-only OAuth flow used by most other clients.

1. In the MCP Client Tool, set the endpoint to https://ai.metricool.com/mcp.

2. Set Authentication to Header Auth.

3. Create a credential with Name X-Mc-Auth.

4. Set the value to your Metricool API key from Account Settings > API.

5. Save the credential and try the workflow again.

Remote MCP custom connectors are available on Claude Free, Pro, Max, Team, and Enterprise. Free users can use only one custom connector at a time.

Remove or replace the existing custom connector, then connect Metricool again. Claude Code still requires a Pro or Max subscription. See How to connect Metricool's MCP with Claude.

Claude Code requires a Pro or Max subscription and installation from the Claude Code product page before you can add Metricool.

1. Confirm Claude Code is installed and you are on Pro or Max.

2. Run:

   claude mcp add --transport http metricool https://ai.metricool.com/mcp

3. Start Claude Code with claude, run /mcp, select Metricool, and authenticate.

Cursor MCP setup requires the Cursor Desktop app. Browser-only Cursor cannot complete the documented install path.

1. Install and open Cursor Desktop.

2. Use the Metricool install deep link or web link from How to connect Metricool’s MCP, or add a custom MCP with:

   "metricool-mcp": {
     "url": "https://ai.metricool.com/mcp",
     "type": "http"
   }

3. Click Connect, authorize Metricool in the browser, and return to Cursor to confirm the connection.

That is usually a plan limit, not a failed server connection. The MCP works on Free and paid plans, but Metricool plan limits still apply to what the MCP can query or schedule.

Check Free-plan examples, client-side requirements, and the MCP vs API boundary in MCP limits and plan requirements. If you need programmatic HTTP access outside an AI client, that is the Metricool API (Advanced or Custom), not MCP. See MCP vs API access: what is the difference?.