Connect the MCP server

The MCP server lets an agent connect to SearchOps through the Model Context Protocol, a standard way for AI tools to read external data. Once connected, an agent can answer questions using your live SearchOps data, like "how did our worst-ranking location do this month?"

What you'll need

A plan that includes API access (Pro and above).
A SearchOps API key. See Getting started with the API.
An MCP-capable client.

Connect

Create an API key in Settings under API access if you have not already.
In your MCP client, add a new server pointing at the SearchOps MCP endpoint:
```
https://searchops.co.uk/api/mcp
```
Provide your API key as a bearer token when the client asks for credentials, the same lp_live_ key used by the REST API.
Confirm the connection. The client should list the SearchOps tools it can now use.

The server uses streamable HTTP, which the common MCP clients support out of the box.

What an agent can do

Once connected, the agent has read access to your account through these tools:

list_locations and get_location
list_location_keywords
list_scans and get_scan
list_reports and get_report

So an agent can, for example, list your locations, pull a location's recent scans, and read the full grid results of a specific scan to summarise where you are losing visibility.

Note: Like the REST API, this access is read-only. The agent can read your data but cannot run scans or change anything.

Security

Your key scopes the agent to your account only. Treat it like a password, and revoke it from Settings if it is ever exposed. Revoking immediately cuts off any client using it.

Warning: Only connect MCP clients you trust with read access to your account data.

Troubleshooting

Client cannot connect: check the endpoint URL and that your key is valid and from a plan with API access.
Tools do not appear: reconnect the server, and confirm the key was accepted.

Next steps

New to API keys? Start with Getting started with the API.