Cursor

Before you start

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

Create the config file

Cursor reads MCP servers from two places. Pick one:

~/.cursor/mcp.json covers every project on your machine. Create the .cursor folder if it does not exist.
.cursor/mcp.json at the root of a repo covers that project and is shared with your team. It holds no credential, so it is safe to commit.

Paste this in:

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

Turn it on and sign in

Open Cursor’s settings and enable socialrouter under MCP, also reachable from Customize in the sidebar. The same toggle switches it off later without deleting the entry.The server then asks you to log in, and Cursor shows a Needs login button next to it. Clicking it opens the SocialRouter consent screen in your browser. Approve, and Cursor holds the token from then on. Each teammate signs in as themselves, and everyone is billed for what they run.

Using an API key instead

A key works everywhere a browser flow does not. Add a header and no login is ever requested:

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

Create the key in the dashboard. It is shown once, at creation. In a committed project config, point at an environment variable rather than pasting the key: "Authorization": "Bearer ${env:SOCIALROUTER_API_KEY}".

Ask for something

In Agent mode:

Get me Satya Nadella’s LinkedIn profile.

Cursor picks up the SocialRouter tools whenever they are relevant. If you are not sure what to ask, try “What social media data can you pull with SocialRouter?”

If something goes wrong

The server stays red and never connects

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 mcp.json.

The key comes through empty

Cursor reads ${env:…} from the environment it was launched with, and opening it from Spotlight or the Dock does not load your shell profile. Either export the key from a place the GUI sees, or paste it into the global ~/.cursor/mcp.json, which nothing commits.

Next steps

Tools reference

What list_services, run, get_extraction and get_account do.

Skills

Ready-made workflows Cursor reads from .cursor/rules/.

Getting started

Clients

Reference

Before you start

If something goes wrong

Next steps

Tools reference

Skills

​Before you start

​If something goes wrong

​Next steps

Tools reference

Skills

Before you start

If something goes wrong

Next steps