Abency
Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.
Read social analytics and schedule posts to live accounts.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Metricool MCP server connects a Metricool social media account to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists seven tools: five read analytics, brand settings and scheduled posts, and two write posts to live social accounts. Sign-in is OAuth, and the connector works on any Metricool plan including Free.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
createScheduledPost and updateScheduledPost act on real social profiles. Metricool's confirmation mechanism is a link in the LLM's reply, not an approval step, so nothing blocks an agent from queueing a post you did not read.mcp-remote instead of the standard connector path.readOnlyHint and destructiveHint flags, parameter schemas and per-tool descriptions are not available to an anonymous client. The read/write split above is inference from names and vendor prose.metricool/mcp-metricool, which returned HTTP 404 on 2026-09-08. The mcp-metricool package on PyPI does resolve, at version 1.1.9, last uploaded 2025-10-07 — which is older than the connector surface described here.Yes. Two of the seven listed tools write, and what they write reaches live audiences. Metricool's own help centre states you can publish content immediately, schedule it for a date and time, or use its best-time option. The connector grants an AI client permission to see, create and publish posts in any connected network, so a scheduled post can go out publicly without a second confirmation step in Metricool.
Any plan, including Free. Metricool's help centre states MCP access does not require a paid plan, and that your existing plan limits still apply afterwards. Free accounts cannot schedule more than 20 posts and reach only 30 days of analytics history. The separate Metricool API is a different product and needs an Advanced or Custom plan, so a token-based client path is not the same as MCP on Free.
OAuth 2.0 with an authorization code grant, verified live on 2026-09-08. An anonymous request returned HTTP 401 with a Bearer challenge naming a resource metadata document, which advertises exactly two scopes. Metricool also documents two alternatives: a header token named X-Mc-Auth carrying your Metricool API key, used by N8N, and METRICOOL_USER_TOKEN with METRICOOL_USER_ID in a client configuration.
More than the seven tools suggest. Metricool's help centre lists nine permission categories the authorization grants: brands and network connections, metrics and reports, creating and publishing posts, Smartlinks, inbox messages and post comments, Google Business Profile reviews, Ads campaigns, autolists, and folders in any connected Canva or Drive account. Metricool describes this as full access similar to signing in directly.
Metricool's help centre lists ten networks: Instagram, TikTok, LinkedIn, Facebook, X, YouTube, Pinterest, Threads, Bluesky and Twitch, plus campaign data from Meta Ads, Google Ads and TikTok Ads. Anthropic's directory description instead claims 13 networks. The two figures come from the same vendor and disagree, so treat the help centre's enumerated list as the checkable one.
From the AI client, not from Metricool. Metricool's troubleshooting article states plainly that you cannot revoke that connector permission from inside Metricool, so you disconnect it wherever you authorized it. In Claude that is Settings, then Connectors, then the three-dot menu beside Metricool and Disconnect. Reconnecting means repeating the client's authorization steps.
Metricool documents an external Claude Desktop bug that blocks the usual connection path, and gives mcp-remote as the workaround. You add a local server entry running npx mcp-remote against the Metricool endpoint, save the config and restart Claude Desktop. Claude.ai and Claude Desktop otherwise share one connection, and Claude Code connects separately over HTTP from the command line.
Three vendor-facing surfaces disagree. Anthropic's directory snapshot lists camelCase names, Metricool's help centre writes create_scheduled_post and update_scheduled_post in snake_case, and its marketing page writes post_schedule_post and update_schedule_post. The server is gated, so no live handshake can break the tie. Ask your client which tools it loaded rather than relying on any published list.
https://ai.metricool.com/mcp — HTTP 401 with WWW-Authenticate: Bearer naming the resource metadata document (2026-09-08). No tool was called and no credential was supplied. · retrieved 2026-09-08mcp:read and mcp:write · retrieved 2026-09-08authorization_code and refresh_token grants, S256 and plain PKCE, dynamic client registration · retrieved 2026-09-08mcp-metricool (checked 2026-09-08, version 1.1.9). The GitHub repository the vendor names returned HTTP 404 the same day. · retrieved 2026-09-08robots.txt on both metricool.com and help.metricool.com allows these paths, and neither carries a Content-Signal directive (checked 2026-09-08) · retrieved 2026-09-08Connect Metricool Social Media Management once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.