Connect Gemini CLI
Google's terminal agent. Uses httpUrl for remote servers.
Want the explained version rather than the config? Read the full Gemini CLI walkthrough, which covers what each setting does and the four failures that waste the most time.
Global: ~/.gemini/settings.json · Per project: .gemini/settings.json
Before you start
Create an API key in the app under Settings, then API Keys. Grant only the permissions this agent needs. The key is shown once. Replace pk_live_xxx in the snippets below with it.
Hosted endpoint
Recommended. Nothing to install, and it stays current without you upgrading anything.
{
"mcpServers": {
"planpost": {
"httpUrl": "https://mcp.planpo.st/mcp",
"headers": { "Authorization": "Bearer pk_live_xxx" },
"timeout": 10000
}
}
}Local install
Runs the MCP server on your own machine through npx, so your key never leaves it. Needs Node 18 or newer.
{
"mcpServers": {
"planpost": {
"command": "npx",
"args": ["-y", "planpost-mcp"],
"env": { "PLANPOST_API_KEY": "pk_live_xxx" }
}
}
}Things that catch people out
- Gemini CLI uses httpUrl for streamable HTTP, not url. The wrong key is a silent no-op.
Check it works
Ask the agent to list your connected accounts. If it comes back with them, all 47 tools are available.
Which social accounts do I have connected on planpo.st?