{
  "markdown": "# Ravenpost MCP server\n\nSchedule and publish social media posts from an AI assistant.\n\n[Ravenpost](https://ravenpo.st/) is a multi-platform social media scheduler —\nInstagram, TikTok, X, Telegram, Facebook, LinkedIn, Threads, Bluesky, YouTube\nand Pinterest. This repository documents its **hosted MCP server**, which\nexposes the\nsame posting flow to any MCP client: list the accounts you have connected,\nupload or reshape media, preview a post exactly as each network will render it,\nthen publish it now, schedule it, or drop it into a weekly posting queue.\n\nThe server is hosted. There is nothing to install and nothing to run.\n\n```\nhttps://api.ravenpo.st/mcp\n```\n\nTransport: **Streamable HTTP**. Official registry entry:\n[`st.ravenpo/ravenpost`](https://registry.modelcontextprotocol.io/v0/servers?search=ravenpost).\n\n## Connecting\n\nTwo ways, and the first needs no credential handling at all.\n\n**OAuth (recommended).** Add the URL above as a custom connector and sign in\nwhen your client opens Ravenpost. The server is an OAuth resource server —\n`/.well-known/oauth-protected-resource` names the authorization server and the\n`401` carries the challenge — so a client that speaks MCP authorization runs the\nwhole flow on its own.\n\n**Personal access token.** For clients with no browser flow. Generate one in\nRavenpost under Settings → MCP tokens (shown once, revocable at any time):\n\n```bash\nclaude mcp add --transport http ravenpost https://api.ravenpo.st/mcp \\\n  --header \"Authorization: Bearer rvp_your_token\"\n```\n\nClients that cannot set headers can pass it in the URL instead —\n`https://api.ravenpo.st/mcp?token=rvp_…`.\n\nYou need a Ravenpost account with at least one connected social account. The\nfree plan is enough to try it.\n\n## Tools\n\n22 tools. Every one declares a title and read-only / destructive hints, so your\nclient can tell you what a call will do before you allow it.\n\n### Accounts\n\n| Tool | What it does |\n|---|---|\n| `list_workspaces` | Every workspace the credential can act in. With more than one, the other tools require a `workspaceId` rather than guessing which client you meant. |\n| `list_accounts` | Connected accounts with their ids, platforms and status. |\n\n### Posts\n\n| Tool | What it does |\n|---|---|\n| `list_posts` | List posts, filtered by status or platform. |\n| `get_post` | One post with every destination's status and permalink. |\n| `preview_post` | Render a post as each platform will show it **without creating anything** — an interactive card in clients that support MCP Apps, and per-platform character counts everywhere else. |\n| `create_post` | Draft, publish, schedule or queue a post across any set of accounts. |\n| `update_post` | Edit a draft or scheduled post — resets it to draft, so pass an action to re-send it. |\n| `delete_post` | Delete the Ravenpost copy and cancel a pending publish. |\n| `schedule_post` | Move a post to a new time. |\n| `publish_post` | Publish a post immediately. |\n\n### Media\n\n| Tool | What it does |\n|---|---|\n| `upload_media` | Upload an image or video from a URL, a local path (dev only) or base64; images are reformatted to the platform shape you name. |\n| `create_media_upload` | Presigned direct upload — for large or production files, so bytes never pass through the model's context. |\n| `attach_media` | Register a direct upload as an asset, reformatting an image or recording a video as-is. |\n| `create_variants` | Cut one image into several platform canvases at once, cropping on the subject rather than the middle. |\n| `list_media` | Recent media assets, to reuse one instead of re-uploading. |\n| `image_formats` | The image formats and target dimensions `upload_media` accepts. |\n\n### Analytics\n\n| Tool | What it does |\n|---|---|\n| `get_analytics` | Followers per account and engagement on recent posts. |\n| `best_times` | Recommended posting hours measured from this workspace's own posts — with an explicit \"not enough data yet\" answer rather than a confident guess. |\n\n### Reference\n\n| Tool | What it does |\n|---|---|\n| `list_audio` | Search Instagram's licensed audio catalog for a reel track. |\n| `list_queue_slots` | The weekly posting schedule and the next free slot. |\n| `list_boards` | The Pinterest boards each connected account owns — a pin has to name one, and Pinterest has no default. |\n| `platform_limits` | Caption budgets, media rules and recommended specs per platform. |\n\n## Two things worth knowing\n\n**Preview before publish.** `preview_post` writes nothing. It returns the post\nas each destination renders it, together with the warnings a picture cannot\ncarry: a caption over the tightest selected platform's limit, a network that\nrequires media when there is none, a thread aimed at a platform with no thread\nmodel, audio outside a reel. A preview that looks right and stays quiet about a\nrejection is worse than no preview.\n\n**It refuses to guess your workspace.** A credential acts as a *user*, and a\nuser can run several workspaces (one per client, on the Agency plan). Ask a\nworkspace-scoped tool with more than one available and it errors, naming them,\nrather than posting one client's content to another's accounts.\n\n## Links\n\n- Product: <https://ravenpo.st/>\n- What the MCP server does: <https://ravenpo.st/mcp/>\n- Tool reference: <https://ravenpo.st/docs/mcp/>\n- REST API: <https://ravenpo.st/docs/api/>\n- Privacy: <https://ravenpo.st/privacy/> · Terms: <https://ravenpo.st/terms/>\n- Support: support@ravenpo.st\n\n## About this repository\n\nDocumentation and the registry manifest (`server.json`) for a hosted service.\nRavenpost's own source is not public. Issues about the MCP server are welcome\nhere; anything account-specific should go to support.\n",
  "bytes": 5667,
  "sha": "8977408f98655b1c84e8fd7c4f8b8ab3ffb4d7e62ed4bcb062a20d7c3cc857ae",
  "repo_slug": "target1m/ravenpost-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_st_ravenpo_ravenpost_32eaf012/readme"
}