How each brand is performing on social, what is scheduled next and who wrote in.
Connect Metricool with your user token and user ID and Memtro reads the account's brands and networks, metric timelines such as followers, impressions and clicks, post analytics, the planner's scheduled posts and social inbox conversations, comments and reviews. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can schedule, draft, move, delete or restore posts, reply publicly to comments and reviews, send direct messages, add internal notes and manage brand tags. Scheduled posts publish publicly, and replies and messages reach people outside the company.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Metricool tool, reads what it needs, and answers with the source cited.
These tools change something in Metricool. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Metricool is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Metricool + MemtroHow did Instagram impressions change last month for the Acme brand?
What are we posting next week, and on which networks?
Which Instagram reels got the most comments in October?
Who has messaged us on Instagram this week?
Move Thursday's pricing post to next Monday at 09:00
At the month-end review the marketing lead asks how Acme did on Instagram. Memtro reads the follower and impressions timelines for the month with their totals, then the reels with the most reach and comments, and puts both into a short summary for the team.
Priya Nair spots a scheduled post about pricing that legal has not seen. She asks Memtro to move it to next Monday and note why. Memtro reschedules the post in the planner and adds an internal note, seen by the team only.
The teams that lean on Metricool most, a question each of them asks, and what they connect beside it.
A record in Metricool is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Metricool's API needs an Advanced or Custom plan, so open Account settings → API in Metricool and copy the user token and user ID
Regenerating the token invalidates the old one and stops this connection, and acting on posts or the inbox needs a user with full access to the brand's planner and inbox
In Memtro open Connections → Metricool, paste the User token and User ID, optionally add the Default brand ID, the blogId in the browser address when viewing a brand, and connect
Ask what the brand is posting next week, and on which networks
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Metricool tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal note to a scheduled post (never creates or publishes a post); add an internal note to a contact in the social inbox (seen by the team only, never sent); add existing brand tags to planner posts (keeps their other tags); schedule a post to publish on a brand's networks, or save it as a draft; move a scheduled post to a new date and time; delete a scheduled post; restore a deleted scheduled post; reply publicly to a comment on a brand's post; reply publicly to a review of the brand; send a direct message in a social inbox conversation; create a brand tag. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
User token and user ID. Metricool's API needs an Advanced or Custom plan, so open Account settings → API in Metricool and copy the user token and user ID.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
