The MCP server is built into postqueen
postqueen now ships a Model Context Protocol server inside the app. There is no companion process to install, no bridge to keep alive and no wrapper repo to clone. The endpoint is part of the same service that runs your dashboard, and your API key is the only credential involved.
What shipped
Three ways to connect, because MCP clients disagree about where secrets belong. Clients that accept a single link take the key in the URL. Clients that prefer headers send it as a bearer token. OAuth capable clients use the /mcp-oauth endpoint, which issues mcp:read and mcp:write scopes, so you can hand an agent read access without handing it publish rights.
- https://api.postqueen.ai/mcp/YOUR_API_KEY for one link setup.
- https://api.postqueen.ai/mcp with Authorization: Bearer YOUR_API_KEY.
- https://api.postqueen.ai/mcp-oauth with the mcp:read and mcp:write scopes.
Once connected, an assistant can draft and schedule posts, pick channels, set publish times, generate and attach images or video, list what is queued and pull analytics. Agent actions land in your normal queue, so you can review, edit or delete anything before it goes out. Channel passwords never reach the assistant, and revoking the API key cuts off every agent at once.
How to try it
Generate a key under Settings, then Developers. In Claude Code it is one command. Claude Desktop and Cursor take the same URL in their MCP config block.
claude mcp add --transport http postqueen \ https://api.postqueen.ai/mcp/YOUR_API_KEYThe server is included with every plan at no extra cost, and agent actions draw on your normal plan limits. Self-hosted installs get the same endpoints on their own domain from the same free Docker image. Source and issues: https://github.com/GkhanKINAY/postqueen-app.