io.github.lukBB/planpost
PlanPost
Is the PlanPost MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Schedule posts to 7 social networks, render video and carousels, read analytics and revenue.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
The server needs auth, so these tool definitions were read from the publisher's open-source package npm:planpost-mcp, started in a container with placeholder values and the network off, on 2026-11-14. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32000,"message":"Provide your PlanPost API key: Authorization: Bearer pk_...- Endpoint
- https://mcp.planpo.st/mcp (streamable-http)
- Host
- mcp.planpo.st
- Of a 1M window
- 1.5 % of a 1M context window
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.planpo.st/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server api.planpo.st, PKCE S256, grants authorization_code, refresh_token.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/lukBB/planpost-mcp
- Website
- https://planpo.st/mcp
- Registry
- active, updated 2026-11-09 · registry entry
Compare this server with others.
More servers
Servers that mention analytics or carousels.
- JustIdea Agency agency.justidea/justidea-agency · alive
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
- Analytics Legends — SAP AI & Analytics MCP Server ai.analyticslegends/sap-analytics · alive
- AutoRFP.ai ai.autorfp/mcp · needs auth
- AwrAIter — Telegram channels ai.awraiter/telegram · needs auth
- Web Analytics ai.b77/web-analytics · needs auth
- BAMF.ai ai.bamf/bamf · not MCP
- Eevy ai.eevy/mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.