Gemini CLI

Gemini CLI supports MCP servers over streamable HTTP through its settings.json configuration, so her 11 tools land 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

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

Replace YOUR_API_KEY with your actual key.

Scope	File it writes	Applies to
none (default)	`.gemini/settings.json` in the current project	That project only
`--scope user`	`~/.gemini/settings.json`	Every project

Manual configuration

You can also edit ~/.gemini/settings.json directly. Gemini CLI uses the httpUrl key for streamable HTTP servers, and the key can sit in the URL or in a header.

Key in the URL
Bearer token

~/.gemini/settings.json

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

Point httpUrl at the bare /mcp endpoint and pass the key in a headers object:

~/.gemini/settings.json

{
  "mcpServers": {
    "postqueen": {
      "httpUrl": "https://api.postqueen.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

The equivalent one-liner:

gemini mcp add --transport http postqueen https://api.postqueen.ai/mcp --header "Authorization: Bearer YOUR_API_KEY"

Keys per the official Gemini CLI MCP documentation: httpUrl is the streamable HTTP endpoint (url is reserved for SSE servers, and PostQueen does not use SSE). A project-level .gemini/settings.json uses the same format.

Your API key grants full access to your PostQueen workspace: treat it like a password. Since the bare gemini mcp add writes into the project’s .gemini/settings.json, keep that file out of version control, and keep the user-level file private too. If the key leaks, regenerate it in Settings > Developers > Public API and update every client that uses it.

Self-hosted

On a self-hosted instance, replace https://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

Start Gemini CLI and run the built-in slash command:

/mcp

It lists configured servers with their connection status and discovered tools. postqueen should show as connected with 11 tools. Then ask:

“List my connected social media accounts”

Your channel names come back, because Gemini reached for her integrationList tool. She is connected.

Next steps

Tools reference

Every parameter of the 11 tools Gemini 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

Gemini CLI as an agent

A worked example: two posts about the release you just cut

Start here

Connect over MCP

Talk to her

Add via CLI

Manual configuration

Self-hosted

Verify

Next steps

Tools reference

Examples

Limits and troubleshooting

Gemini CLI as an agent

​Add via CLI

​Manual configuration

​Self-hosted

​Verify

​Next steps

Tools reference

Examples

Limits and troubleshooting

Gemini CLI as an agent

Add via CLI

Manual configuration

Self-hosted

Verify

Next steps