Any other app

SocialRouter is a standard remote MCP server over Streamable HTTP, with nothing app-specific about it, so any app that speaks MCP can connect: Windsurf, Zed, Cline, Continue, your own project.

https://mcp.socialrouter.io/mcp

Before you start

A SocialRouter account, and that is all. Nothing to install and no local process. Sign up at socialrouter.io. How you authenticate depends on what your app supports. If it implements OAuth for remote MCP servers, it will offer to sign you in and you never handle a credential. If it does not, send an API key as a bearer header. Authentication covers both.

The block to paste

If your app can sign you in, give it the URL and nothing else:

{
  "mcpServers": {
    "socialrouter": {
      "type": "http",
      "url": "https://mcp.socialrouter.io/mcp"
    }
  }
}

Otherwise, add your key:

{
  "mcpServers": {
    "socialrouter": {
      "type": "http",
      "url": "https://mcp.socialrouter.io/mcp",
      "headers": {
        "Authorization": "Bearer sr_live_your_key_here"
      }
    }
  }
}

Create the key in the dashboard. It starts with sr_live_ and is shown once, at creation. Three things differ between apps. The top-level key is mcpServers almost everywhere and servers in VS Code. The URL field is url almost everywhere and httpUrl in Gemini CLI. And "type": "http" is required by some apps, ignored by the rest — it is harmless either way.

Check it works first

Before touching any app config, confirm the endpoint answers you:

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 response containing "serverInfo" means your credential and your connection are both fine. A 401 means it is wrong, revoked, or missing from the header.

What the server expects


Transport	Streamable HTTP, `POST` only (it is stateless, so `GET` and `DELETE` answer `405`)
Auth	`Authorization: Bearer <credential>` on every request, either an API key or an OAuth access token. The server treats them the same
Discovery	`/.well-known/oauth-protected-resource/mcp` (RFC 9728), also advertised on the `401` as `WWW-Authenticate: … resource_metadata=…`
Session	none — no `Mcp-Session-Id` to keep or send back

If you are writing the client yourself, the OAuth path is the ordinary one: an unauthenticated request answers 401 with a pointer to the metadata document, which names the authorization server. Clients register dynamically, so there is no client ID to issue by hand.

Apps that only run local servers

A few apps still start MCP servers as a local process instead of calling a URL. For those, and for offline work, the same server ships as an npm package. It authenticates with an API key and needs Node.js on your machine:

{
  "mcpServers": {
    "socialrouter": {
      "command": "npx",
      "args": ["-y", "@socialrouter/mcp"],
      "env": {
        "SOCIALROUTER_API_KEY": "sr_live_your_key_here"
      }
    }
  }
}

Same four tools, same catalogue. Prefer the URL whenever your app supports it: there is no version to keep up to date.

Getting started

Clients

Reference

Before you start

The block to paste

Check it works first

What the server expects

Apps that only run local servers

Dedicated guides

Claude Code

Claude Desktop

Cursor

Codex CLI

VS Code

Gemini CLI

​Before you start

​The block to paste

​Check it works first

​What the server expects

​Apps that only run local servers

​Dedicated guides

Claude Code

Claude Desktop

Cursor

Codex CLI

VS Code

Gemini CLI

Before you start

The block to paste

Check it works first

What the server expects

Apps that only run local servers

Dedicated guides