MCP (Model Context Protocol) is the standard way to plug an outside tool into an AI assistant. Connect SocialRouter once and the assistant you already use can pull public social data on demand: new leads, enrichment for a list of accounts, what competitors are publishing, or buying signals in the places your market talks. It is the same catalogue as the API. You ask in plain language, the assistant picks the service, and you get the data back.

​
One URL, nothing to install

SocialRouter is hosted. You point your assistant at this URL, and sign in when it asks.
There is nothing to download and no version to keep up to date. New platforms and services show up on their own.

​
Connect your app

Each guide is a short copy-paste, five minutes at most.

Claude Code

One command in your terminal.

Claude Desktop

Settings → Connectors → Add custom connector.

Cursor

One small file, then a toggle in settings.

Codex CLI

One command, or a few lines of config.

VS Code

For GitHub Copilot in agent mode.

Gemini CLI

One command, or a few lines of config.
Using something else, like Windsurf, Zed, Cline or your own app? The generic setup works anywhere.

​
What you need

An account, and that is all. Sign up at socialrouter.io. When your assistant connects for the first time it opens a browser, you approve it, and it holds the credential from then on. There is no key to create or store. An API key still works, sent as a bearer header, and it is what you want for a client that cannot open a browser, or for a config shared with a team. Authentication covers both, and how to see and revoke what you have connected.

​
Your first request

Once the app shows SocialRouter as connected, just ask:
Get me Satya Nadella’s LinkedIn profile.
Pull this week’s top posts from r/SaaS and summarise the recurring complaints.
Here are 20 LinkedIn company pages. Give me headcount and industry for each, as a table.
Two things make the answers better. Name the platform, since “get the LinkedIn profile of…” works better than “get the profile of…”. And paste real URLs when you have them: profile, post and page links are the most reliable input there is. To see what is possible, ask the assistant itself: “What social media data can you pull with SocialRouter?” It lists every platform and service, with the price per record.

​
What it costs

Nothing runs until you ask for it. You pay per record returned, out of your credit balance, and credits explains how that works. Ask “What’s my SocialRouter balance?” at any time, or check the dashboard. On a big job, two things help. Ask for a limit (“only the first 20”), and ask the assistant what the job will cost before it runs.

​
Is it safe

Your credential is held by your app and sent to mcp.socialrouter.io over HTTPS on each request. When you sign in, that credential is a token bound to this endpoint alone: it cannot be used against the rest of your account. Every app you approve shows up in the dashboard, with its own usage, an optional spending cap and a button to disconnect it. If you lose the machine, that is the button to press. The server keeps no credential of its own and stores nothing between requests: it can only ever spend the credits of whoever is calling. If you use an API key instead, treat the config file holding it like a password file. Authentication covers when a key is the better choice. The server only reads public data. It never posts or changes anything on your behalf, and you never connect a social account of your own to it. Scraped bios, comments and post text come from strangers on the internet, so the server labels them as untrusted content when it hands them to the assistant. The assistant reports on that text and ignores any instruction hidden inside it.

​
Going deeper

Tools reference

The four tools, their parameters, and how routing works under the hood.

What you can pull

Every platform and service the assistant can call.