Skip to main content
She speaks MCP over streamable HTTP, so any client that can reach a remote MCP server connects with a single URL, with no local process and no wrapper package. Whatever the client calls the field, it wants the same three things: an endpoint, your API key and a name.
You need your PostQueen API key first. In the app at app.postqueen.ai, open Settings > Developers > Public API and click Reveal.
Your API key can post to every account you have connected, so treat it like a password. Whether it sits in the URL or in an Authorization header, it ends up in a config file on your machine, so keep those files out of version control and off shared screens. If the key leaks, regenerate it in Settings > Developers > Public API and update every client that uses it.

Streamable HTTP

One endpoint with the key in the path.

Bearer header

The same endpoint, key in an Authorization header.

Stdio only

For clients that cannot reach a remote server yet.

​
Any MCP Client

For any other client, these are the only details that matter.

​
Streamable HTTP URL

Most clients ask for a single endpoint. Put the API key in the path:
The config key differs by client. url, httpUrl, and serverUrl are all in use, so check your client’s docs for which one it expects for streamable HTTP.

​
Bearer Header

If your client supports custom headers, keep the key out of the URL instead:
Both forms use the same key and give you the same 11 tools. Pick whichever your client takes more cleanly.

​
Self-Hosted

On a self-hosted instance, swap the host for your NEXT_PUBLIC_BACKEND_URL:
Most self-hosted setups serve the backend under /api, so the MCP path sits at /api/mcp. Use whatever NEXT_PUBLIC_BACKEND_URL is set to, then append /mcp/YOUR_API_KEY. 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.

​
Stdio-Only Clients

Some clients only launch local processes over stdio and have no way to enter a remote URL. Bridge the gap with mcp-remote, which runs on your machine and forwards stdio traffic to PostQueen over HTTP. It needs Node.js.
Some stdio clients (Cursor and Claude Desktop on Windows) mangle spaces inside args. If the Bearer form fails there, put the whole header value in an environment variable and pass it without spaces, for example "--header", "Authorization:${AUTH_HEADER}" with AUTH_HEADER set to Bearer YOUR_API_KEY in the entry’s env block. The bridge is a fallback, not an upgrade. If your client can reach a remote URL on its own, use that instead, for fewer moving parts and no Node.js dependency.

​
Verify

Whichever client you wired up, ask it:
“List my connected social media accounts”
Your channel names come back, because the agent reached for her integrationList tool.
The server connected but discovery returned nothing, which usually means the key is wrong or truncated. Reveal it again in the PostQueen app and paste it in full, with no surrounding whitespace or quotes.
Confirm your client is using the streamable HTTP transport rather than stdio, that it kept the trailing key segment in the URL, and that nothing on your network blocks api.postqueen.ai. On self-hosted setups, check that the reverse proxy forwards /mcp and does not buffer streaming responses.
That combination means the endpoint is right but the key was rejected. Regenerate the key in Settings > Developers > Public API and update the config, remembering that the URL form carries the key in the path while the Bearer form carries it in the Authorization header. The Bearer prefix itself is stripped if present, so either spelling of that header works and a missing prefix is never the cause.

​
Next Steps

MCP Tools

See what all 11 tools can do

Examples

Real prompts and the tool calls they trigger