One MCP Server for a Dozen Platforms: From Install to Your First Post, With Prompts You Can Paste

Your agent writes a decent launch post in twenty seconds. Getting it onto Instagram took you an evening: the Graph API wants a public image URL, your S3 link got rejected, and the token you finally got works for your test account but not for the real one. YouTube and LinkedIn are still you, clicking upload.

That’s the normal state of agent-driven marketing right now. Writing got cheap and posting didn’t. This page sets up one MCP server that takes the posting off your hands, then gives you a week of prompts to paste so the setup actually gets used.

Where the time actually goes

People building this themselves keep hitting the same three walls.

Platform plumbing. An n8n user automating Instagram found the API “requires the image to be available via a publicly accessible URL,” then went through Catbox (unreliable), ImgBB (URLs rejected) and S3 (requests failed) looking for one that worked (r/n8n). Someone automating Meta ads through Claude uploaded images to the media library and the agent “always says ‘image not found’ despite being successfully there on my end” (r/ClaudeAI). Another developer spent “over 2 weeks” on an Instagram integration that worked for test users and returned Invalid OAuth 2.0 Access Token for real ones (r/n8n).

The last mile. An OpenClaw user has their agent drafting for six channels from a JSON content calendar, and says the drafting “works great.” The posting doesn’t: “the last mile from ‘scheduled’ to ‘posted’ is me sitting there clicking buttons on 5 different platforms” (r/openclaw).

Context. Skills are easy to install and don’t know your product. The author of an open-source Claude Code plugin with 166 marketing skills built a /bootstrap command for exactly this reason: it interviews you about your brand and audience, because without that you get “generic marketing advice” (r/ClaudeAI). They’re right about the order. Product context comes first, and the skills only help once it exists.

The setup below handles all three: AutoWhisper holds the platform connections, hosts the media and publishes. It learns the product from your URL. Your agent just talks to it.

Step 1: Install (two minutes)

Pick one.

Let the agent do it. Paste this into Claude Code, Cursor, OpenClaw or any agent that can follow instructions from a URL:

Connect me to AutoWhisper — follow the instructions at https://autowhisper.xyz/skill

It installs itself and gives you a link. Open it and click Approve. No account yet? The approval page signs you up first, then brings you back to approve.

Add the remote MCP server yourself. The endpoint is https://autowhisper.xyz/mcp and it uses OAuth. In Claude Code:

claude mcp add --transport http autowhisper https://autowhisper.xyz/mcp

Then type /mcp inside Claude Code, pick autowhisper, and choose Authenticate. In claude.ai or another client that supports custom connectors, add the same URL as a connector and approve.

Either way, check it worked:

Call autowhisper_status and tell me which workspace I'm in and what's connected.

To cut every agent off later: Settings → Connect your agent → Disconnect. Every connected agent stops working at once.

Before you go further, set up permissions so reads never prompt you and publishing always does. The settings block is in Let Your AI Agent Do Marketing Without Wrecking Anything. It takes a minute and it’s the reason you’ll leave this connected.

Step 2: Connect your accounts once

Connect my Instagram, LinkedIn and YouTube to AutoWhisper. Give me the links to authorise each one.

The agent hands you one OAuth link per platform. You click through each once, logged in as yourself. After that AutoWhisper does the publishing. Your agent never handles a platform token, never hosts an image, and never needs a Meta developer app.

What publishes automatically: TikTok, YouTube, Instagram, Facebook, X, LinkedIn, Threads, Bluesky and Pinterest. Posts go out at the times your audience is usually active in their own time zone, with a daily cap per platform (LinkedIn gets one a day) and a per-platform number of hashtags.

Ad accounts work the same way. Connect a Meta, TikTok or LinkedIn ad account once, and set Starting budget per ad under Workspace settings → Ad channels. Ads get built there paused, and you start them yourself.

Each connected social account or ad account costs 80 credits a month, so connect the two or three channels your buyers actually use, not all nine. Then check:

Call autowhisper_platforms. Is every channel connected and healthy?

Step 3: Let the AI CMO read your product

Add my product https://yourapp.com and start the CMO. Tell me what you think it does, who it's for, and the three strongest reasons someone would try it.

Give it a real URL. The CMO reads the page and builds a product profile from it; a text description alone won’t create a product. Read what it says back. If it gets the buyer wrong, correct it now, in plain words: “It’s for agency owners, not freelancers.” Everything it writes later starts from this.

For software, it captures pages from your site and uses your real interface in product demo videos, with the text on screen kept as it is. If the screens that matter are behind a login, upload screenshots instead. Three formats fit software best: UGC-style talking videos, product demos, and animated explainers (rendered in code, voiced in the workspace’s language, about 25 seconds, and cheaper than a full video).

This is why one connected tool beats a hundred generic skills. The context sits with the product, not in a prompt file you have to keep current, and the CMO learns from every draft you approve or reject.

Step 4: Get the first post out

Make two UGC videos and one product demo for this product. Put them in the review feed; don't publish anything.

A full video costs 52 credits. The script and first frame are charged when the draft is made, and the render when you approve it. New accounts start with 65 credits.

Show me the review feed. For each draft, give me the hook and the first line of the script.

Approve one. The agent calls autowhisper_action, gets back a confirmation id, and should show you what’s about to happen before calling autowhisper_confirm. Once you say yes, the post is scheduled to every connected channel that fits its format.

A week of prompts

Here’s a routine that takes a few minutes, three times a week. Paste as-is, or save each one as a slash command.

Monday: make this week’s batch

Check my credit balance and what's still waiting in the review feed. Then make this week's batch for my main product: three short videos, each built on a different reason to buy, not three versions of the same one. Leave everything in the feed for me to review.

Show me the new drafts with their hooks. I'll tell you which to approve. Ask before you confirm anything.

Wednesday: check what’s running

Call autowhisper_posts. What went out since Monday, what's scheduled, and what failed? For each failure, tell me the reason and whether a retry will help or I need to reconnect the channel.

Retry the failed posts where a retry can help. Show me each confirmation before you confirm it.

Friday: look at results, decide next week

Call autowhisper_performance for the last 7 days. Which channels sent visits and which sent nothing? What did the ads spend? Keep the numbers apart from your interpretation, and tell me when a sample is too small to mean anything.

Based on that, which reason to buy should next week's batch push harder, and which should we drop? Ask the CMO, then tell me what it said.

Rejecting a draft is also feedback. Say why (“too salesy,” “wrong buyer”). The CMO uses it in the next batch. For what to look at in the Friday numbers, see Signal Tracking.

Common questions

I have more than one product line, or I’m doing this for clients. Use one workspace each. Every workspace has its own products, its own connected accounts, its own content language and its own CMO chat. autowhisper_status lists them with ids. Tell the agent to pass workspace_id on every call. Without it, some tools fall back to your current workspace and others to the first one on the account. Before You Start covers the workspace gotchas in more detail.

The videos came out in the wrong language. The workspace sets the content language, not the language you type in. Chat in English inside a Spanish workspace and you get Spanish. For a one-off, say it: “Make this one in German.”

A post failed. Ask for autowhisper_posts. Failed rows say why and whether a retry can help. “Needs reconnect” means a person has to re-authorise that channel; the agent can’t do that for you. Everything else can be retried through autowhisper_action with retry_post.

I approved something and nothing was posted. If no channel was connected at the moment you approved, nothing got scheduled, and connecting a channel afterwards doesn’t go back for it. Connect first, then approve. The result line from the approval says which happened.

Can it post to Reddit or Substack? No. The list in step 2 is the list.

What to do next

Open your agent and paste the first prompt from step 1. Then run step 3 with your homepage before you connect anything else. Reading back the CMO’s summary of your product tells you within a minute whether the drafts will be worth reviewing. No account yet? Create one here, or let the approval page do it.