ravenpost
Start free
Model Context Protocol

Your social scheduler, inside Claude

Ravenpost runs an MCP server. Connect it once and an assistant can write, schedule and publish across 9 networks for you — 20 tools over the same services and the same validation the dashboard runs on. No browser automation, no second set of rules.

Start freeHow to connect

On every plan, the free one included · one token, one workspace · revocable in a click

20 tools · one conversation

What the assistant can actually do

Everything the dashboard does, minus the clicking. Each card lists the real tool names — they are generated from the server’s own registrations, not written out here.

See where it can post

Your workspaces and every connected account, with platform and status — so the assistant names real destinations instead of guessing at them.

  • list_workspaces
  • list_accounts

Write, schedule, publish

One caption fanned out to any set of accounts, with a different caption per network, threads, replies and quotes. Publish now, schedule a time, or drop it in the queue.

  • list_posts
  • get_post
  • create_post
  • update_post
  • delete_post
  • schedule_post
  • publish_post

Prepare the media

Upload an image or video, cut one photo into every network’s canvas at once, or hand it a presigned URL so a 200 MB file never travels through the conversation.

  • upload_media
  • create_media_upload
  • attach_media
  • create_variants
  • list_media
  • image_formats

Ask what actually worked

Followers and per-post engagement, plus the best hours to publish measured from your own posts — with an explicit “not enough data yet” rather than a made-up hour.

  • get_analytics
  • best_times

Reel audio

Search Instagram’s licensed audio catalog and attach a track to a reel — the only native music path any of these platforms exposes.

  • list_audio

Know the rules first

Caption budgets, media counts and posting-queue slots, read from the same registry the publisher enforces — so limits are checked before a post is written, not after it is rejected.

  • list_queue_slots
  • platform_limits

Every tool, with what each one takes and returns: the MCP reference.

Step 1 · Your token

Get a token

One personal access token authenticates both the MCP server and the REST API. It is created in the dashboard, because minting a credential is something only a signed-in page should do.

  1. 1Open dashboard Settings → API tokens and generate one. Name it after the client you are connecting — the name is how you tell two apart later.
  2. 2Copy it there and then. It starts rvp_ and it is shown once — we keep only a SHA-256 hash and a short prefix, so we cannot show it to you again.
  3. 3It carries the workspace it was minted in. Revoke it from the same page at any time; connected clients lose access immediately.
Create a tokenI don’t have an account yet
Step 2 · Connection

Point your client at it

One endpoint, https://api.ravenpo.st/mcp. How the token travels is the only thing that differs between clients.

One command in the terminal

Claude Code sends the token as a bearer header — the form to prefer wherever a client supports it.

Add the server
claude mcp add --transport http ravenpost https://api.ravenpo.st/mcp \
  --header "Authorization: Bearer rvp_your_token_here"

claude mcp list
Step 3 · In use

Things to ask it

Paste one in once you’re connected. The assistant picks the tools; the server keeps it inside every limit.

Which social accounts do I have connected on Ravenpost?

Draft a post about our new pricing page for Instagram, X and LinkedIn. Give X its own shorter caption and show me all three before you schedule anything.

Take this image, cut it for an Instagram feed post, a story and LinkedIn, and attach the right one to each destination.

What’s my best hour to post on LinkedIn, based on my own numbers?

Schedule this to the next free slot in my posting queue.

Which of last month’s posts got the most engagement, per platform?

Turn this into a five-tweet thread and post the first one as a reply to my launch tweet.

What are the caption limits for the networks I have connected?

Where the limits are

What it will not do

Handing an assistant your accounts is a reasonable thing to hesitate over. These are the answers, and they are enforced on our side rather than asked of the model.

It cannot invent media

The media tools ingest files you provide — a URL, a base64 blob, a presigned upload. Nothing here generates an image or a video, and nothing bills you for generation credits.

The platform rules are the server’s, not the model’s

Caption budgets, media requirements, TikTok’s compliance fields, thread caps. A post that would breach one is rejected with the reason — never silently truncated to fit.

It asks which workspace

With more than one workspace, every tool requires you to name it and the error lists them. Publishing one client’s content to another’s accounts is the failure this design exists to prevent.

A draft stays a draft

Creating a post and publishing it are separate actions. Nothing goes live because a conversation drifted — publishing is a step the assistant has to take on purpose.

The token is hashed, scoped and revocable

We store a SHA-256 hash and a short display prefix; the token itself is shown once. It carries one user and one workspace, and revoking it from Settings cuts access immediately.

Same engine as the dashboard

The server builds a fresh session per request over the dashboard’s own services — no second implementation to drift, no shared state between clients or workspaces.

Questions

What is an MCP server, in one sentence?+

Model Context Protocol is the open standard for giving an AI assistant real tools instead of a browser to click around in — so Claude talks to Ravenpost over an API and gets structured answers back, rather than screenshotting a dashboard.

Which networks can the assistant post to?+

All 9 we support: Instagram, TikTok, X, Telegram, Facebook, LinkedIn, Threads, Bluesky, YouTube. One post fans out to as many connected accounts as you pick, and each destination keeps its own status, permalink and error.

Does it cost extra?+

No. The 20-tool MCP server, the REST API and webhooks are on every plan including the free one. Your plan's limits — connected accounts, posts per month — apply the same way whether a post comes from the dashboard or from a conversation.

Do I have to use Claude?+

No. The endpoint speaks Streamable HTTP and is stateless, so any MCP client works — Claude Code, Claude Desktop, claude.ai custom connectors, Cursor, or something you wrote yourself. Claude is what most people arrive with, not a requirement.

Can it post something without me seeing it first?+

It can, if you ask it to publish — that is the point of the tool. What it cannot do is exceed the limits: a post is created as a draft unless an action says otherwise, platform rules are enforced server-side, and every published post appears in the dashboard with its own status and permalink, so nothing happens off the record.

Is putting the token in a URL safe?+

It is a fallback for clients that cannot send headers — claude.ai and Claude Desktop custom connectors. We never log request URLs server-side, and any token can be revoked at once. Where your client supports a header, use the header form.

Connect it in about two minutes

Free plan, no card. Generate a token, paste one command, and ask your assistant what you have connected.

Start freeRead the reference