Ravenpost
Start free
For AI agents

The social scheduler your agent can actually use

An MCP server and a REST API over the same service the dashboard calls — so an assistant can list your accounts, upload media, draft, schedule and publish to Instagram, TikTok, X, Telegram, LinkedIn, Threads, Bluesky, YouTube and Pinterest, then read back what each network did with it. On every plan, free one included.

Start free Read the tool reference
Add it to any MCP client
https://api.ravenpo.st/mcp

What an agent actually needs

Publishing is easy to expose and hard to expose well. These four are where the difference shows up.

A credential it can get by itself

The server is an OAuth resource server, so a client that speaks MCP authorization needs only the URL — it discovers the rest and runs the sign-in. Personal access tokens still exist for headless clients, scoped to one workspace and revocable from the dashboard.

A way to look before it writes

`preview_post` takes the arguments of a real post, writes nothing, and returns it as each network will render it — plus the warnings that would otherwise become a rejection. In clients that support MCP Apps it comes back as an interactive card, so what somebody approves is the post rather than a JSON object.

One call that reaches everywhere

One post fans out to any set of connected accounts across 9 networks, with a different caption per network, threads, replies and quotes. Each destination keeps its own status, permalink and error, so a partial failure is legible instead of a red dot.

An honest no

A tool that guesses is worse than one that refuses. With more than one workspace, the server names them and asks rather than picking the first — which is what stops one client’s post landing on another’s accounts. The same rule covers a missing Pinterest board, a caption over budget, and a platform we have stopped offering.

Two ways in

MCP server

22 tools across 7 groups, over Streamable HTTP. Stateless — a fresh session per request, so there is nothing to keep in sync between clients.

  • Accounts
  • Posts
  • Media
  • Analytics
  • Instagram
  • Pinterest
  • Reference
Endpoint
https://api.ravenpo.st/mcp
Every tool, with its arguments

REST API

20 endpoints on the same surface, for when the thing publishing is your code rather than a conversation. Bearer token, JSON, webhooks, and an OpenAPI document generated from the same table that renders the reference.

Publish to every connected account
curl -X POST https://api.ravenpo.st/v1/posts \
  -H "Authorization: Bearer rvp_your_token_here" \
  -H "Content-Type: application/json" \
  -d '{"caption":"We shipped it.","accountIds":["…"],"action":"publish"}'
Full endpoint reference

Set it up in your assistant

Claude

What changes once it is connected

Read the guide

ChatGPT

ChatGPT cannot post to social media by itself

Read the guide

Claude Code

It is the same server, from the command line

Read the guide

Cursor, Windsurf, Goose, n8n or something you wrote: point it at the endpoint above. Anything that implements MCP authorization needs nothing else.

Readable without opening a page

Every one of these is generated at build time from the same source as the docs, so it cannot describe a product we no longer ship. Every page on this site also has a Markdown twin at the same path with .md appended.

ai-catalog.json

The interfaces this domain exposes to be called, not read. Pointed at from robots.txt.

llms.txt

What the product is, which URL answers which question, and when not to reach for us.

openapi.json

All 20 endpoints, checked against the API’s own controller by a test.

Where it can publish

Scale your social presence for half the price

Every paid tier is roughly half its Postiz equivalent. Cancel anytime.

Free

Try it out with one account.

$0/mo

Free forever

  • 1 social account
  • 10 posts / month
  • Every platform we support
  • Calendar, posting queue & media library
  • Analytics for Instagram, TikTok, X & Facebook
  • MCP server for Claude & other AI assistants
  • 1 seat
Start free

1 seat

Starter

For solo creators getting consistent.

$14/mo

vs Postiz $29/mo

  • 5 social accounts
  • Unlimited posts
  • Everything in Free
  • 1 seat
Get Starter

1 seat

Most popular

Growth

For creators and brands running several accounts.

$24/mo

vs Postiz $49/mo

  • 15 social accounts
  • Unlimited posts
  • Everything in Starter
  • Email support
  • 3 team seats
Get Growth

3 seats

Agency

For power users running a large account portfolio.

$49/mo

vs Postiz $99/mo

  • 50 social accounts
  • Unlimited posts
  • Everything in Growth
  • Priority support
  • Unlimited team seats
Get Agency

Unlimited seats

Common questions

What is the difference between the MCP server and the REST API?

Who is calling. MCP is for an assistant in a conversation — it discovers the tools, signs in with OAuth and asks. The REST API is for your own code, with a bearer token and an OpenAPI document. They are the same service underneath, so a post created by one is visible to the other. Both are on every plan, free included.

Which agents does this work with?

Anything that speaks MCP over Streamable HTTP: Claude on web, desktop, mobile and in Claude Code, ChatGPT’s custom connectors, Cursor, Windsurf, Goose, and agent frameworks that ship an MCP client. Anything that does not can use the REST API instead.

Can an agent publish without me seeing it first?

It can, and you decide whether it does. MCP clients ask before running a tool that writes, and our tools declare whether each one is read-only or destructive so the dialog says what it will do. Tell the agent to draft or schedule only and it will — a scheduled post sits on the calendar where it can be read and cancelled.

Can an agent generate the images or video?

Not through us. The media tools ingest a file you provide — a URL, an upload, or something already in your library — and reformat images to each network’s canvas. Nothing here synthesises media; if the agent has its own image model, hand us the result.

What are the rate limits?

The REST API allows a fixed budget per minute per token — the reference states the exact number — and every response says what happened per destination. Publishing itself is queued, so a fan-out to ten accounts is one call, not ten.

How much does agent access cost?

Nothing extra. The MCP server and the REST API are included on every plan including the free one — plans differ by how many accounts you connect, not by which interfaces you may call.

Comparing the options?

Best social media MCP servers →

Seven schedulers with an MCP server, ranked by the cheapest plan it is reachable on — including where each one beats us.

Best social media scheduling APIs →

The same comparison for products with a REST API, and what each one leaves you to build.

Give your agent somewhere to post

One connected account and ten posts a month, free forever. No card.

Start free