Ravenpost
Schedule and publish social media posts from Claude. Ravenpost is a social media scheduler for content creators, influencers and agencies: write a post once, send it to Instagram, TikTok, X, LinkedIn, Threads, Bluesky, YouTube, Pinterest and Telegram, and see how each network will show it before anything goes out.
This plugin connects Claude to Ravenpost's hosted MCP server and adds four skills that teach Claude the workflow around it: settle the workspace and the accounts, preview before writing anything, and publish only when you ask.
What you can do
- Preview a post as every network will show it, before anything is created, with a warning for anything a network would reject: a caption over X's 280 characters, a post with no media where one is required, a Pinterest pin with no board.
- Draft, schedule, queue or publish to one account or several at once — at a time you name, or in the next free slot of your weekly posting queue.
- Edit, reschedule or cancel posts that have not gone out yet, and check how a published post landed on each account.
- Bring in images and video from a link, and reshape one image into each network's format.
- Read followers and engagement for the accounts each network lets Ravenpost measure.
Getting started
- Create a Ravenpost account at ravenpo.st — the free plan is enough to try it — and connect your social accounts in the dashboard. Connecting a social account happens there, not in Claude.
- Add the plugin, then connect Ravenpost from its Connectors tab and sign in when asked. There is no API key to copy: the server uses OAuth.
- Ask Claude, for example:
- "Preview a launch post for my Instagram and X accounts before anything is posted."
- "Schedule the LinkedIn version for Tuesday at 9am."
- "Put this in the queue for all my accounts."
- "What's scheduled for next week, and did yesterday's post go out everywhere?"
- "How are my accounts doing — followers and engagement on recent posts?"
Skills
Data and privacy
The plugin runs nothing on your computer. Its skills are written instructions,
and its one connector is Ravenpost's hosted server at
https://api.ravenpo.st/mcp. When Claude calls a tool, the request — captions,
links to media, the accounts you choose, the times you set — goes to Ravenpost
under your own sign-in, and Ravenpost posts to the networks you selected when
you publish or when a scheduled time arrives.
One other destination, and only for a file you hand over: a large image or
video can go straight into Ravenpost's own storage, a Cloudflare R2 bucket
(*.r2.cloudflarestorage.com), through a one-time upload link the connector
issues (create_media_upload), so its bytes never pass through the
conversation. Nothing is sent anywhere else.
Ravenpost keeps your posts and media until you delete them, and a connected account until you disconnect it; deleting your Ravenpost account erases all of it. Privacy policy: https://ravenpo.st/privacy/.
Good to know
- A published post cannot be taken back through Ravenpost on Instagram, TikTok, Threads or YouTube, and deleting a post in Ravenpost never removes it from a network. That is why Claude previews first and publishes only on your instruction; scheduling and drafting stay changeable.
- Ravenpost does not write captions or generate images. The words and the files come from you or from Claude, and media is brought in from a link you give.
- Some networks report no numbers to Ravenpost. Those are shown as not collected, never as zero.
- With several workspaces — one per client, on the Agency plan — Claude asks which one to use rather than guessing, so one client's post never lands on another's accounts.
Tools
26 tools. Every one declares a title and read-only / destructive / open-world hints, so your client can tell you what a call will do before you allow it.
Accounts
Posts
Media
Analytics
Studio
Reference
Other ways to connect
The server is hosted; there is nothing to install or run.
https://api.ravenpo.st/mcp
Transport: Streamable HTTP. Official registry entry:
st.ravenpo/ravenpost.
OAuth (recommended). Add the URL above as a custom connector in any client
that speaks MCP authorization — Claude, ChatGPT, Cursor, VS Code — and sign in
when it opens Ravenpost. The server is an OAuth resource server:
/.well-known/oauth-protected-resource names the authorization server and the
401 carries the challenge, so the client runs the whole flow on its own.
Personal access token. For clients with no browser flow. Generate one on the MCP page of the Ravenpost dashboard (shown once, revocable at any time):
claude mcp add --transport http ravenpost https://api.ravenpo.st/mcp \
--header "Authorization: Bearer rvp_your_token"
Clients that cannot set headers can pass it in the URL instead —
https://api.ravenpo.st/mcp?token=rvp_….
This repository
Documentation, the registry manifest and the plugin for a hosted service. Ravenpost's own source is not public. Issues about the MCP server are welcome here; anything account-specific should go to support.
plugin.json portable manifest (Agent Plugins 1.0.0), with the
ChatGPT listing and review metadata under
extensions.com.openai
mcp.json the hosted server, Agent Plugins format, OAuth (DCR)
.claude-plugin/plugin.json the same identity, for Claude
.mcp.json the hosted server, Claude format
skills/<name>/SKILL.md one workflow each
skills/publish-a-social-post/references/
tools.md every tool, its arguments and what it returns
platforms.md caption budgets, media rules, per-platform limits
server.json the official MCP registry entry
scripts/package.sh builds the ZIP the ChatGPT plugin portal takes
Both reference files are generated from the server's own tool registrations and platform registry, not transcribed — a skill that describes an argument the server no longer takes is worse than one that says nothing, because the model follows it and the call fails.
Submitting to ChatGPT. OpenAI's plugin portal takes the package as a ZIP
(Plugins → Upload plugin). scripts/package.sh builds it from plugin.json,
mcp.json, skills/, the licence and the icon the site serves — nothing
Claude-only and no credentials (reviewer sign-in goes in the portal's Review
details form). The repository keeps no image of its own: the Claude directory
holds a plugin for review while one sits beside a script that could reach it. The
listing text, the five positive and three negative review cases and the
release notes ride in plugin.json, so changing them means a new version and
a new ZIP; changes to the hosted tools don't — the portal rescans the server.
Links
- Product: https://ravenpo.st/
- What the MCP server does: https://ravenpo.st/mcp/
- Tool reference: https://ravenpo.st/docs/mcp/
- REST API: https://ravenpo.st/docs/api/
- Privacy: https://ravenpo.st/privacy/ · Terms: https://ravenpo.st/terms/
- Support: [email protected]