> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postqueen.ai/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> PostQueen's hosted API is https://api.postqueen.ai. The public API base is https://api.postqueen.ai/public/v1 and takes the raw API key in the Authorization header, with no Bearer prefix.
> The MCP server for posting is https://api.postqueen.ai/mcp/YOUR_API_KEY (or /mcp with Authorization: Bearer YOUR_API_KEY). docs.postqueen.ai/mcp only searches these docs and cannot post.
> The API key is under Connections > API Keys in the app, and only workspace admins can see it.
# Other MCP clients
> Connect any MCP client that is not on the agents list: the address, the header, the config shapes clients use, and a bridge for clients that only run local servers.
Any client that can reach a remote MCP server over streamable HTTP can use PostQueen. Whatever the client calls its fields, it needs the same three things: a name for the server, the address, and your API key, either in the address or in a header. PostQueen has not tested clients that are not on [the agents list](/agents/overview).
**Where the API key is:** in the app, open **Connections > API Keys**. Only a workspace Admin or Super Admin can reveal or rotate it; other members see it masked. A workspace has one key, and each agent card on **Connections** shows your MCP address with the key already filled in.
## The addresses
| Address | How it signs in | Tools |
| -------------------------------------------- | ----------------------------------------------------- | --------------------------- |
| `https://api.postqueen.ai/mcp/YOUR_API_KEY` | The API key is part of the address | 21 |
| `https://api.postqueen.ai/mcp` | Header `Authorization: Bearer YOUR_API_KEY` | 21 |
| `https://api.postqueen.ai/mcp-oauth-dynamic` | Sign in with PostQueen, approved by a workspace admin | 20, all but `ask_postqueen` |
PostQueen has tested the key address (with Claude and ChatGPT) and the Bearer header (with Grok Bot). The sign-in address has not been tested end to end yet. Clients that still use the older SSE transport can connect to `https://api.postqueen.ai/sse/YOUR_API_KEY`.
`docs.postqueen.ai/mcp` is a different server: it searches these docs and cannot post. Use an address from the table above.
Start with the key address. It needs no header and no sign-in, so it works in almost every client. Use the Bearer header when the client has a header field and you want the key out of the address. The sign-in address works only in clients that support MCP sign-in.
## Config shapes
Most clients take the server in one of these shapes. Check your client's docs for which one it reads.
```json mcpServers theme={"system"}
{
"mcpServers": {
"postqueen": {
"url": "https://api.postqueen.ai/mcp/YOUR_API_KEY"
}
}
}
```
```json servers theme={"system"}
{
"servers": {
"postqueen": {
"type": "http",
"url": "https://api.postqueen.ai/mcp/YOUR_API_KEY"
}
}
}
```
```json mcpServers with a header theme={"system"}
{
"mcpServers": {
"postqueen": {
"url": "https://api.postqueen.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
```
The first shape is the one Cursor and Devin Desktop use, and the second is VS Code's. Zed reads `context_servers`, Gemini CLI writes `url` with `"type": "http"`, and Muse Code needs a `schema_version`. Their pages have the exact blocks: [Cursor](/agents/cursor), [VS Code](/agents/vscode), [Devin Desktop](/agents/devin-desktop), [Zed](/agents/zed), [Gemini CLI](/agents/gemini-cli), [Muse Code](/agents/muse-code).
If the client asks for a transport, choose streamable HTTP. Choose SSE only when the client offers nothing else, and then use `https://api.postqueen.ai/sse/YOUR_API_KEY`.
Claude Desktop does not read a remote address from `claude_desktop_config.json`. Add PostQueen in Claude as a custom connector instead: see [Claude](/agents/claude).
## Clients that only run local servers
Some clients can only start a program on your computer and talk to it over standard input and output (stdio). Bridge them to PostQueen with [`mcp-remote`](https://www.npmjs.com/package/mcp-remote), which runs on your computer and forwards the calls. It needs [Node.js](https://nodejs.org/).
```json Key address theme={"system"}
{
"mcpServers": {
"postqueen": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.postqueen.ai/mcp/YOUR_API_KEY"]
}
}
}
```
```json Bearer header theme={"system"}
{
"mcpServers": {
"postqueen": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.postqueen.ai/mcp",
"--header",
"Authorization: Bearer YOUR_API_KEY"
]
}
}
}
```
Use the bridge only when the client cannot take an address. A direct connection has fewer parts that can fail.
## Keep the key safe
The key can post to every channel in your workspace. It sits in the client's config file either way, so keep that file out of version control and off shared screens. If the key leaks, an admin chooses **Rotate key** under **Connections > API Keys**, and you update every client that used it.
## Check that it works
Ask the client's agent:
```text theme={"system"}
List my PostQueen channels.
```
It calls `integrationList` and answers with your connected channels. If the connection fails or no PostQueen tools appear, see [the agent will not connect over MCP](/agents/troubleshooting#the-agent-will-not-connect-over-mcp).
## Next steps
Which agents can post to PostQueen, how each one connects, and what PostQueen has tested.
What each of the 21 tools does, and what an agent cannot do.
The order an agent calls the tools in, with prompts that work.
What to do when a connection or a command fails.