Add ScoutRival to Cursor.
Drop one config block into Cursor's MCP settings and your ScoutRival tools show up in the composer. A read-only token takes about two minutes and spends nothing.
Cursor connects with a pasted token: drop one config block into its MCP settings and your ScoutRival tools appear in the composer. It takes about two minutes, and a read-only token spends nothing.
Your token is shown once and then lives in a plain text file on your machine. Treat that file as a secret — anyone who can read it can read your ScoutRival data. A read-only token can't spend credits or change anything, which is why it's the safe default to start with.
1. Create a token
In ScoutRival, go to Settings → MCP and create a connection token. Give it a label you'll recognise (for example, Cursor on my laptop), leave the access level on Read-only, and copy it — it's shown once and we can only store a scrambled copy. MCP is a Starter-and-up feature; on the Free plan you'll see an upgrade prompt here instead. For what each access level grants, see connection tokens.
2. Add the server
Cursor reads MCP servers from a JSON file. You can add ScoutRival to one project or to every project:
Open the config file
For a single project, create .cursor/mcp.json in that project's root. To use ScoutRival across every project, create ~/.cursor/mcp.json in your home folder instead — it applies to all of them.
Paste the config block
Add the block below, replacing sr_mcp_YOUR_TOKEN with the token you copied. If the file already has an mcpServers object, add the scoutrival entry inside it rather than pasting a second one.
Restart Cursor
Reopen Cursor, or restart it, so it reloads its MCP servers. If your Cursor version offers it, you can also add the server through Cursor Settings → MCP → Add new server and fill in the same URL and token there.
{ "mcpServers": { "scoutrival": { "url": "https://user.scoutrival.com/api/mcp", "headers": { "Authorization": "Bearer sr_mcp_YOUR_TOKEN" } } } }
3. Check it connected
Open Cursor's MCP settings. The scoutrival server should be listed with a green or enabled state and a count of the tools it exposes. If it shows red, the token line or the surrounding JSON is wrong — check that the Authorization value starts with Bearer sr_mcp_ and that every brace and comma is in place.
If the server is enabled but its tools don't appear in the composer, toggle the connection off and on so Cursor re-reads the tool list. That also clears a cached list after ScoutRival adds a tool.
4. Ask in the composer
Once the server shows its tools, ask for your data from the composer or chat:
- "List my ScoutRival brands."
- "Give me today's brief for <your brand>."
- "How visible am I in AI answers?"
If it answers with your real data, you're connected. Read tools are free and return the full dashboard view. To generate content or run a check from Cursor, create a token with the Content or Full access level — read connection tokens first.