VS Code

VS Code uses a servers key where most other apps use mcpServers. Everything else is the same.

Before you start

You need VS Code with GitHub Copilot and agent mode enabled, plus a SocialRouter account. No API key: VS Code signs you in itself. Sign up at socialrouter.io if you have not yet. VS Code connects straight to the hosted endpoint, so there is nothing to install.

Create the config file

Two options. .vscode/mcp.json at the repo root covers that project and is shared with your team. For a config that applies everywhere, run MCP: Open User Configuration from the command palette (⇧⌘P / Ctrl+Shift+P).Either way, the entry holds no credential:

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

Or add it from the command line

code --add-mcp '{"name":"socialrouter","type":"http","url":"https://mcp.socialrouter.io/mcp"}'

Start it and sign in

Run MCP: List Servers from the command palette, pick socialrouter, and start it. VS Code asks to authenticate and opens the SocialRouter consent screen in your browser; approve, and it keeps the token from then on. The same menu opens the server’s log if it fails.In the Chat view, switch to Agent mode and open the tools picker. The four SocialRouter tools appear there.

Using an API key instead

A key works everywhere a browser flow does not. The version below asks for it once and stores it in VS Code’s secret storage, so the repo never sees it:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "socialrouter-key",
      "description": "SocialRouter API key",
      "password": true
    }
  ],
  "servers": {
    "socialrouter": {
      "type": "http",
      "url": "https://mcp.socialrouter.io/mcp",
      "headers": {
        "Authorization": "Bearer ${input:socialrouter-key}"
      }
    }
  }
}

Create the key in the dashboard. It is shown once, at creation. In a user-level config that never leaves your machine you can paste it straight into the header instead. With a header configured, VS Code never asks you to authenticate.

Ask for something

In agent mode:

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

It never asks you to authenticate

A headers block skips the sign-in entirely, because a client holding a credential never asks for one. Remove it if you meant to log in, then restart the server from MCP: List Servers. Authentication has the rest.

Entering a new key after rotating it

VS Code caches inputs after the first prompt. Run MCP: Reset Cached Tools / Inputs from the command palette to be asked for the key again.

Next steps

Tools reference

What list_services, run, get_extraction and get_account do.

What you can pull

Every platform and service Copilot 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