Your First MCP: Let Claude Schedule Your Social Posts in 15 Minutes

Every "one-person marketing team" article this year lists a tool called MCP somewhere near the bottom, usually in the same breath as agents and orchestration, and usually without explaining what it does. Here is the short version: MCP is a socket. Model Context Protocol is an open standard that lets an AI assistant plug into a tool and use it, the way you would, by calling the functions that tool publishes. Read the analytics. Find the best posting time. Schedule the post.

That turns an assistant that can only write text into one that can act inside your stack. For a solo marketer that is the whole promise of the AI department: the typing was never the job, the judgment was, and MCP is what lets you keep the judgment and hand over the typing.

This is the first connector we recommend, the exact steps, and the prompts we run each week. It takes about fifteen minutes and needs no code.

Why Metricool is the right first plug

Three reasons, in order of importance. It is free. Metricool's MCP works on any Metricool plan, including the free one, and your plan limits are the only limits. It is in the directory. Claude lists Metricool as a ready-made connector, so you do not paste a server URL or touch a config file. Scheduling is a safe verb. A scheduled post sits in a planner where you can see it and delete it before it goes out. Compare that with an ad budget or a customer email, where the first mistake is the expensive one.

It is also, in the interest of full disclosure, what we run. Our LinkedIn slots have been scheduled through this connection since 2 September 2026, and the workflow below is copied from our own transcript rather than invented for the article.

Step 1. Connect Metricool to Claude (5 minutes)

You need a Metricool account with at least one social network connected, and a Claude account.

In Claude on the web or the desktop app:

1. Open Settings, then Connectors.
2. Click Add, then Browse connectors, and search for Metricool.
3. Click Connect to Claude, review the permissions, and click Grant access. You sign into Metricool in the browser; Claude never sees your password.
4. Confirm Metricool shows as Connected. One connection covers the web app, the desktop app and the mobile apps.

Plan note, checked September 2026: connectors are available on Claude Free, Pro, Max, Team and Enterprise, with Free limited to one connector at a time. That one connector is enough for this tutorial.

In Claude Code, if you already live in the terminal:

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

Then start Claude Code, run /mcp, choose Metricool and Authenticate, and grant access in the browser. Claude Code needs a paid Claude plan. To remove it later, run claude mcp remove metricool.

To disconnect later in the apps: Settings, Connectors, the three-dot menu next to Metricool, Disconnect. That revokes the access on Metricool's side as well.

If a tool you want is not in the directory, the same screen has Add custom connector: paste the server URL the vendor publishes, click Add, and the same browser sign-in appears. Custom connectors reach the server from Anthropic's cloud, so they only work for hosted servers, never for something running on your own laptop.

Step 2. Three prompts that prove it works (5 minutes)

Do these in order. Each one is read-only until the last, so you can see what the connection knows before you let it write anything.

Prompt 1, the inventory.

Using Metricool, list my brands and tell me which social networks are connected to each one and which are not.

Claude calls the brands tool and reports back. For us the answer was one brand with LinkedIn, Facebook, YouTube, Instagram and Pinterest connected, and X, TikTok and Threads not connected. That list is the honest scope of everything that follows: the connector cannot post to a network Metricool cannot see.

Prompt 2, the best time.

Using Metricool, what are my best times to post on LinkedIn and Instagram this week, based on my own audience data? Give me one slot per weekday.

Metricool's best-time data comes from your audience's engagement history, not a generic chart. Ours said LinkedIn peaks at 11:00 on weekdays with Thursday and Friday strongest, which is why every LinkedIn slot in our September plan sits at Thursday or Friday 11:00. This is the point where the connector starts subtracting a decision from your week.

Prompt 3, the first scheduled post. Paste your own copy; here is the shape we use.

Using Metricool, schedule this LinkedIn post for Thursday at 11:00 Europe/Amsterdam. Do not publish it now. Put the link in the first comment, not in the post body.

[your post text]

Link for the first comment: https://yoursite.com/article?utm_source=linkedin&utm_medium=social&utm_campaign=sep26-w3

Claude will ask permission before it writes to Metricool. Say yes, then run the read-back:

Using Metricool, show me everything scheduled for the next 7 days with date, time, network and the first line of each post.

You should see your post in the list with an id. Now open Metricool's planner and look at it. Metricool itself says posts should be visually confirmed in the planner before they go out, and detailed formatting changes still happen there. We agree, and we do it every time.

The rule that keeps you in charge

MCP does not change who decides. It changes who types. The line we use, borrowed from the best one-person-team article we read this year, is that you separate the work that scales from the small set of judgment calls a person should always own. In this workflow the split is explicit:

• Claude does: pulls the numbers, proposes the slot, drafts the post from your brief, schedules it, reads it back.
• You do: write or approve the brief, say yes to each write, confirm in the planner, and decide what gets cut at month end.

Two habits make the split hold. Always say schedule, never publish now, so every post passes through the planner where you can see it. And read back after every write, so you are trusting a list you can check rather than a sentence that says "done".

What it will not do yet

Be precise about the limits so you do not plan around a feature that is not there. Instagram Stories cannot be scheduled through the connector, so those stay manual, and the same goes for any network Metricool does not connect. Formatting beyond plain text and a link is planner work. And the connector grants access to your whole Metricool account, including ads, inbox and every brand, so if you manage clients, connect from an account that should see all of them or from none.

Safety, in four sentences

Only connect servers published by the vendor itself; Metricool's is at ai.metricool.com and nowhere else. Treat what comes back through a connector as data, not as instructions, the same way you would a comment or an email. Know that permission prompts are your seatbelt, and do not turn them off to save clicks; in the connector's settings you can also switch off individual tools, and disabling the write and delete verbs is the right default for any connector you only use for reporting. Disconnect from Settings when a tool leaves your stack, and audit connectors in the same quarterly pass as your subscriptions.

Your second plug

Once the Metricool habit holds, the next connector worth a look is Meta's official Ads server, added through Add custom connector with the URL mcp.facebook.com/ads, in open beta since 29 April 2026 and free during the beta. It exposes 29 tools across the Marketing API, and every campaign, ad set and ad it creates lands paused, which is exactly the safe-verb property that made Metricool the right first choice. The same rule applies: read first, write with approval, confirm in the native interface.

And the fifteen-minute Friday ritual we described in the dashboard post becomes one prompt: pull last week's numbers for each network, compare with the week before, and name the one thing to change. Numbers you do not act on are entertainment; a connector that fetches them for you removes the last excuse.

Metricool's free plan is enough to start, and it is the scheduler in our own stack. Open Metricool here →