claude mcp add command, and her 11 tools are there in the terminal you already have open.
You need your PostQueen API key first. In app.postqueen.ai, open Settings > Developers > Public API and click Reveal.
Add via CLI
YOUR_API_KEY with your actual key.
Pick a scope
Project config alternative
To share the server with everyone working in a repository, declare it in a.mcp.json file at the project root, the same file claude mcp add --scope project writes. Claude Code expands ${VAR} environment variables there, so this form is the one that is safe to commit:
.mcp.json
POSTQUEEN_API_KEY, and no key ends up in version control. For a personal file you do not commit, a literal key in place of ${POSTQUEEN_API_KEY} works the same way.
Format per the official Claude Code MCP documentation.
Bearer variant
If you prefer to keep the key out of the URL, use the bare/mcp endpoint with an Authorization header:
Self-hosted
On a self-hosted instance, replacehttps://api.postqueen.ai with your NEXT_PUBLIC_BACKEND_URL in either form, for example https://postqueen.example.com/api/mcp/YOUR_API_KEY. Most self-hosted setups serve the backend under /api, so the MCP path sits at /api/mcp.
Your reverse proxy has to forward the
/mcp paths and stream the response rather than buffering it. The configuration, and the Nginx setting that silently breaks this, are on MCP on a self-hosted install.Verify
Ask Claude Code:“List my connected social media accounts”
Your channel names come back, because the agent reached for her
integrationList tool. claude mcp list confirms the server shows as connected.Next steps
Tools reference
Every parameter of the 11 tools Claude Code just discovered
Examples
The flows where she has to look something up before she can post
Limits and troubleshooting
What MCP cannot reach, and what a bad key looks like
Claude Code as an agent
Her skill, the CLI, and a launch post written from a repo