Docs: System guides

Read Metricool into Maplith

Brands, connected social channels, scheduled posts and metric totals by period: how the social media team plans and reports.

Social media planning and analytics · Also known as Metricool social media, Metricool planner · Checked 2026-10-27

On this page

Best path

Recommended: your agent fetches it. Metricool's hosted MCP server lets an agent that has signed in read the brands, the scheduled posts and the metric totals by period. Maplith's own integration reads the same server on the workspace's scan schedule, once it is open to the workspace. Metricool's separate API-key server is a different connection.

Try the paths in this order:

Your agent fetches it, with the access you already gave it. Connectors a vendor or client page confirms: Metricool MCP in ChatGPT (by its URL); Metricool MCP in Claude Code (by its URL). The agent connects Metricool's hosted MCP server by its URL, signs in to Metricool, and reads the brand settings, the posts scheduled ahead and, for each connected network, the metrics it offers and their totals for a past period. It never calls the tools that create, change or send posts for review.
Maplith reads an MCP server you already run. Metricool runs Metricool MCP. Its address is https://ai.metricool.com/mcp. Documentation: help.metricool.com. The hosted server uses OAuth: approve read access in the browser. Metricool's separate API-key server is a different connection. The hosted server offers read tools and tools that change posts. Maplith's integration calls only the read tools for brands, scheduled posts, the metrics a network offers and their totals, and not the best-time-to-post suggestions, which describe no part of the business. Maplith reads this server through its own integration, described below; you cannot add it under Data sources › Systems as a server you run.
Export files, the fallback that always works. See the export steps below.
Maplith’s own integration. Built, and not open to every workspace yet. Until it opens, share the export. See Maplith’s integration below.

Datasets that make a good map

Dataset	One row is	Key columns	Joins to
Brands and channels	One brand and its connected networks, including its time zone.	brand id, brand label, network, time zone	Scheduled posts, metric catalogue and analytics by brand id and network.
Scheduled posts	One post planned for a future date on one or more networks.	scheduled post id, brand id, publication date, draft or approval state	Brands by brand id.
Metric catalogue	One metric id found for a network, with its label and aggregation rule.	metric id, network, connector, metric label, aggregation rule	Analytics by metric id and network.
Analytics	One aggregate value per metric, brand, network and requested period; no individual published posts.	brand id, network, metric, period start, period end, value	Brands and channels by brand id and network; metric catalogue by metric id and network.

Columns are named, never their values. Maplith tries to mask personal data such as email addresses, but that is best effort: you decide what goes in.

The access to give

Who usually has the rights: The Metricool account owner, or a team member with access to the brands to be read.

Choose the narrowest access that covers the data:

Sign in to Metricool when the client connects its MCP server, and approve its access
Access to each brand the map should cover

Where to click:

In the AI client, add a connector or MCP server with the address https://ai.metricool.com/mcp
Sign in to Metricool in the browser window that opens
Approve the access, then ask the agent to list the brands

A key or token made here stays in the tool that reads the system, never in a chat. Maplith asks for one only under Data sources › Systems in the app.

Export steps

Format: CSV Date range: The last three months

Metricool's help describes no CSV of a network's metric totals; your agent or Maplith's integration reads them.
Scheduled posts: export the posts of the Calendar or an Autolist to CSV from the Planner.
Brands and channels need no file of their own: the scheduled-posts file names its brand and network.
Repeat for each network and brand the map should cover, and upload the files in Data sources › Scans.

How much data

About 10–100 scheduled posts and a few hundred metric totals per brand a month (an estimate). Estimate for a small team planning about a post a day on a few networks and tracking a few metrics per network, not a measured figure.

An agent that reads rows through a chat reads every one of them, about one token per four characters. Above a few thousand rows a dataset, or for a daily refresh, an MCP server or an export is the better path.

Maplith’s integration

Status: Built, and not open to every workspace yet. Until it opens, share the export.

How to connect

In Maplith, open Data sources › Systems and choose Connect Metricool. You need to be an admin or builder of the workspace.
Metricool asks you to sign in and approve read access for Maplith: approve it there. Maplith asks for Metricool's read scope only.
Metricool returns you to Data sources › Systems. Maplith checks that it is you, in the workspace you started from, before it stores anything; the access is sealed and never shown again.
Scan it from the connection, or wait for the workspace's scan schedule.

Before anything is stored, Maplith checks:

The request started in your workspace in the last 15 minutes and was not changed on the way
You are the same person who started it, still signed in, and still an admin or builder of that workspace
Connecting Metricool is open in that workspace and it has no Metricool connection yet
Metricool's server answers and offers the read tools, before the access is stored

The permissions it asks for

Permission	Why
`mcp:read`	Reads brands, scheduled posts, the metric catalogue and metric totals by period; mcp:write is never requested.

What it reads

Brand settings and connected networks, posts scheduled for the next 90 days, the metrics each network offers and their totals by period over the last 90 days, through the hosted server's read tools
Tables of brands, channels, scheduled posts, metrics and their totals, read during the scan and deleted when it ends; Maplith tries to mask personal data as in uploaded exports
What Maplith keeps is the map, and the totals of any metric you choose to track; individual published posts and campaigns are not kept

What it never reads or does

Anything that changes Metricool: the server's tools that schedule or update a post are never called
Inbox messages, comments, reviews, SmartLinks, competitor profiles or connected Canva and Drive files
Metricool's write scope: it is never asked for
Your Metricool access anywhere but sealed in Maplith: it is never shown again and never sent to a model

Choosing what is read: Maplith reads every brand the account can see, up to 25, over the last 90 days and the next 90; there is no filter to set. To read less, share Metricool's CSV exports instead of connecting.

Scans. The connection is scanned on your workspace’s scan schedule, daily or weekly. The first scan is one you ask for from the connection; after that it follows the schedule.

Events. Metricool sends no events Maplith can receive, so changes arrive with the next scan.

Removing it. Remove under Data sources › Systems deletes Maplith's sealed copy of the access and the connection. Metricool offers no endpoint for Maplith to revoke its access itself, so the page says so. To end the access in Metricool too, revoke Maplith's access in your Metricool account. The map built from Metricool stays, marked as no longer maintained. Signals stay for their retention. The playbooks Maplith set up for it are taken out of use, not deleted.

What Maplith sets up once it is connected

Maplith sets these up itself. You correct them; you never have to approve them first. If the system is disconnected, the playbooks Maplith set up and nobody changed are taken out of use, and put back when it is connected again.

Signals it raises:

Something Maplith relies on stopped working (checked on a schedule): a regular check finds the access revoked or lapsed, the server unreachable, or a read tool Maplith needs changed or gone
A connected system grew or shrank (checked on a schedule): the connection offers at least a quarter more or fewer resources than at the last check
New finding (checked on a schedule): a scan finds a flaw in how posts are planned or reported, such as a channel nobody posts to

Checks:

Connection check (every 12 hours): checks that Metricool still grants the access and offers its read tools, and calls none of them
Read allow-list (on every call): refuses any Metricool tool that is not one of its read tools before a request is sent

Suggested playbooks:

Reconnect Metricool. Starts when the Metricool connection's “Something Maplith relies on stopped working” signal is raised.
Review a change in the social channels. Starts when a scan finds a channel or a field of Metricool's data added or gone.

Schedules:

Read Metricool (with the workspace's scan schedule, daily or weekly): the map of brands, connected channels, schedules and metric totals by period stays current

Always

Read-only, and never a credential sent to Maplith through a chat.
The same recent period, a few months, from every system.
You decide what goes in.

Sources

Written from public documentation, last checked 2026-10-27:

← All system guides · Markdown version