Gemini CLI

Google’s Gemini CLI connects to Social media studio’s remote Streamable HTTP MCP server using an httpUrl and an X-API-Key header.

You need an API key (format sk_live_...) to connect. Generate one from Settings > API Access, or see Authentication.

Setup

Run the CLI command

gemini mcp add --transport http so-me-studio \
  https://api.so-me.studio/mcp \
  -H "X-API-Key: sk_live_xxxxxxxxxxxxxxxxxxxxxxxx"

Verify the connection

Run /mcp in a Gemini session to see so-me-studio listed with its tools.

Alternative: settings.json

Edit the settings file directly:

Scope	File Location
Global	`~/.gemini/settings.json`
Project	`.gemini/settings.json` in project root

settings.json

{
  "mcpServers": {
    "so-me-studio": {
      "httpUrl": "https://api.so-me.studio/mcp",
      "headers": {
        "X-API-Key": "sk_live_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Gemini CLI uses httpUrl (not url) for Streamable HTTP transport.

Troubleshooting

Server not listed / no tools

Confirm you used the httpUrl field and that the X-API-Key value is an active key beginning with sk_live_. Restart the Gemini CLI session after editing settings.json.

405 Method Not Allowed

The Social media studio server runs in stateless Streamable HTTP mode (POST only). Use httpUrl as shown — do not configure an SSE url.

MCP Server

Other Agents

Setup

Alternative: settings.json

Troubleshooting

​Setup

​Alternative: settings.json

​Troubleshooting

Setup

Alternative: settings.json

Troubleshooting