Connect your client

PostQueen speaks MCP over streamable HTTP, so any MCP-compatible client connects to her with a single URL. Pick the client you work in below, or take the endpoint straight to your own config.

Add her to your client

Get your key first. In app.postqueen.ai, open Settings › Developers › Public API and click Reveal. Swap it for YOUR_API_KEY below.

claude mcp add --transport http postqueen https://api.postqueen.ai/mcp/YOUR_API_KEY

Add --scope user to make her available in every project. Full options: Claude Code.

{
  "mcpServers": {
    "postqueen": {
      "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY"
    }
  }
}

Into .cursor/mcp.json, or use the Settings UI: Cursor.

codex mcp add postqueen --url https://api.postqueen.ai/mcp/YOUR_API_KEY

Written to ~/.codex/config.toml: Codex.

gemini mcp add --transport http postqueen https://api.postqueen.ai/mcp/YOUR_API_KEY

Add --scope user for every project: Gemini CLI.

No file to edit. Both take the URL in their connector screen:

https://api.postqueen.ai/mcp/YOUR_API_KEY

Step by step: Claude, ChatGPT.

{
  "mcpServers": {
    "postqueen": {
      "serverUrl": "https://api.postqueen.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:POSTQUEEN_API_KEY}"
      }
    }
  }
}

The header form keeps the key out of the file. Anything else: Other clients.

The connector URL contains your API key, and that key can post to every channel you have connected. Treat it like a password. If the key leaks, regenerate it in Settings > Developers > Public API and update every client that uses it.

Pick your client

Claude Code

Add PostQueen with one claude mcp add command

Claude

Connect through the desktop app on macOS or Windows

Claude Web & Mobile

Add PostQueen as a connector on claude.ai

ChatGPT

Turn on developer mode, then paste the URL as a connector

Cursor

One .cursor/mcp.json entry, or the Settings UI

Codex

One block in ~/.codex/config.toml, key in or out

Gemini CLI

One mcpServers entry in your settings file

Other clients

The generic remote shape, for anything that speaks MCP

Self-hosted

Replace https://api.postqueen.ai with whatever your NEXT_PUBLIC_BACKEND_URL is set to, then append /mcp/YOUR_API_KEY:

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

Once connected, ask your AI agent:

“List my connected social media accounts”

Your channel names come back, because the agent reached for her integrationList tool.

Your assistant is connected. It can see your channels and it can put a post on your calendar. Nothing else to install.

When nothing comes back

The client shows no tools at all

Read the status code before changing anything, because it says which endpoint form you are actually on:

Status	What it means
`401 Missing Authorization header`	You are on the Bearer form and the header is not arriving
`401 Invalid API Key or OAuth token`	Bearer form, and the token is wrong or revoked
`400 Invalid API Key`	You are on the URL form. Also what a `pos_` OAuth token gets here, because the path form only ever looks a value up as an API key

Responses on these routes are plain text rather than JSON, so some clients show them as a bare “server error” with the real message only in a log.

It connected, and then every call fails

Connecting proves less than it looks. Both forms answer the browser’s preflight with a 200 and permissive CORS headers before any key is checked, so a client can report success while holding a key that does not work. The first real call is the honest one.

Self-hosted, and it just hangs

Almost always the reverse proxy buffering the response. MCP streams, and a proxy that holds the whole reply, or that talks HTTP/1.0 upstream, breaks it while leaving the rest of the app working. MCP on a self-hosted install has the working blocks and a curl that isolates it.

It worked yesterday

Check whether the API key was regenerated. Rotating it in Settings > Developers > Public API takes the old one out immediately and every client still holding it stops mid conversation. PostQueen keys never rotate on their own.

Next steps

Tools Reference

Every parameter and every field the eleven tools send back

Examples

Discord channels, video voices, and the flows that need a lookup first

Limits and troubleshooting

What MCP cannot reach, and what a bad key looks like

MCP on a self-hosted install

Your own URL, and the proxy setting that breaks the stream

Start here

Connect over MCP

Talk to her

Add her to your client

Pick your client

Claude Code

Claude

Claude Web & Mobile

ChatGPT

Cursor

Codex

Gemini CLI

Other clients

Self-hosted

Verify

When nothing comes back

Next steps

Tools Reference

Examples

Limits and troubleshooting

MCP on a self-hosted install

​Add her to your client

​Pick your client

Claude Code

Claude

Claude Web & Mobile

ChatGPT

Cursor

Codex

Gemini CLI

Other clients

​Self-hosted

​Verify

​When nothing comes back

​Next steps

Tools Reference

Examples

Limits and troubleshooting

MCP on a self-hosted install

Add her to your client

Pick your client

Self-hosted

Verify

When nothing comes back

Next steps