Gemini CLI

Before you start

You need Gemini CLI and a SocialRouter account. No API key: Gemini signs you in itself. Sign up at socialrouter.io if you have not yet. Gemini connects straight to the hosted endpoint, so there is nothing to install.

Run one command

gemini mcp add --transport http socialrouter https://mcp.socialrouter.io/mcp --scope user

--scope user writes to ~/.gemini/settings.json and makes it available everywhere. The default scope is the project, which writes to .gemini/settings.json instead.

Inside a Gemini CLI session:

/mcp auth socialrouter

Gemini opens your browser on the SocialRouter consent screen. Approve, and it keeps the token from then on.

Using an API key instead

A key works everywhere a browser flow does not. Add the header when you create the server:

gemini mcp add --transport http socialrouter https://mcp.socialrouter.io/mcp --scope user -H "Authorization: Bearer sr_live_your_key_here"

Or write settings.json yourself:

{
  "mcpServers": {
    "socialrouter": {
      "httpUrl": "https://mcp.socialrouter.io/mcp",
      "headers": {
        "Authorization": "Bearer $SOCIALROUTER_API_KEY"
      }
    }
  }
}

Gemini expands $VAR_NAME and ${VAR_NAME} from your environment, so a project-level settings.json in this form is safe to commit: each teammate exports their own key. Create keys in the dashboard. With a header configured, no sign-in ever runs.

Check it is connected

Type /mcp inside a Gemini CLI session to list the connected servers and their tools.

Ask for something

Get me Satya Nadella’s LinkedIn profile.

If you are not sure what to ask, try “What social media data can you pull with SocialRouter?”

If something goes wrong

The server fails to connect

Call the endpoint yourself to see the real answer:

curl -X POST https://mcp.socialrouter.io/mcp -H "Authorization: Bearer sr_live_your_key_here" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"0"}}}'

A 401 means the credential is wrong, revoked, or missing from the header. Anything else with "serverInfo" in it means the endpoint is fine and the problem is in settings.json.

The server shows as needing authentication

Run /mcp auth socialrouter to sign in again. A headers block in settings.json takes precedence and skips the sign-in entirely, so remove it if you meant to log in. Authentication has the rest.

Nothing shows up under /mcp

Check which scope you wrote to: a project-level .gemini/settings.json only applies when you launch Gemini from that folder. Re-run the command with --scope user to have it everywhere.

Next steps

Tools reference

What list_services, run, get_extraction and get_account do.

What you can pull

Every platform and service Gemini can call.

Getting started

Clients

Reference

Before you start

If something goes wrong

Next steps

Tools reference

What you can pull

​Before you start

​If something goes wrong

​Next steps

Tools reference

What you can pull

Before you start

If something goes wrong

Next steps