Skip to content
MCP server / Connection guide

Connect Serge to your
LLM client

This guide connects Claude, Cursor, or a backend integration to your Serge workspace over MCP. Choose read-only OAuth or an explicitly scoped API key, verify the workspace and permissions, then read measurement data or provision a site.

Need

A Serge workspace and an MCP client. Reading uses traffic:read; automated site provisioning also needs an API key with sites:write.

Endpoint

All clients connect to https://mcp.serge.ai.

Best for

Read-only measurement in Claude or Cursor, plus deliberate server-to-server site provisioning with an API key.

1

Choose how to authenticate

Pick one of two methods. You don't need both.

API key

Mint a key in Settings → API keys. Use traffic:read for measurement. For AgentSolo provisioning, choose the preset granting exactly sites:write + traffic:read. Keep the key in a server-side secret store.

OAuth

Add https://mcp.serge.ai as a connector in Claude and sign in with your Serge account. OAuth remains read-only: it can query your data, but cannot call create_site.

2

Configure your client

Open your Claude Desktop config file (Cursor uses the same JSON shape under its MCP settings):

macOS ~/Library/Application Support/Claude/claude_desktop_config.json
Windows %APPDATA%\Claude\claude_desktop_config.json

Add Serge under the mcpServers object. Replace the placeholder with your sk_serge_ key:

Using read-only OAuth instead? Skip the config file: in Claude, add https://mcp.serge.ai as a connector and sign in. Provisioning still requires an API key with sites:write.

3

Restart and verify the connection

Restart your client so it loads the new server. The Serge tools should appear in the tool picker.

Confirm the connection is bound to the right workspace by asking your client to call whoami:

It returns the workspace and scopes. Measurement needs traffic:read. AgentSolo provisioning must show exactly sites:write and traffic:read; if not, create a replacement key and rotate safely.

4

Ask your first question

Use plain language. Your client maps the question to the right tool and fills in the period and domain.

If a tool replies site_not_found, a read-only connection should call list_sites. With a provisioning key, call create_site, paste the returned snippet into the tenant site, deploy, then call check_install until it reports receiving.

What you can ask

Traffic"How many AI assistants visited yourstore.com this week, and which platforms?"
Buy-intent"What share of assistant traffic on yourstore.com was real buy-intent versus crawlers?"
Session endings"Show me sessions classified as abandoned or a short bounce on yourstore.com, with their entry and exit pages."
Verification"Was any platform verified on yourstore.com last week by a valid HTTP message signature or a vendor-published source IP range?"

More example prompts

Which entry pages do AI assistants land on most on yourstore.com?

Walk me through one abandoned or short-bounce session on yourstore.com page by page, without inferring why it ended.

Compare buy-intent traffic on yourstore.com over the last 7 days versus the last 30.

Which sessions self-declared as ChatGPT but passed neither valid-signature nor published-IP verification?

Turn signals into an investigation

When recorded session paths repeatedly end on the same page, use them as a starting point for investigation — not as a diagnosis. Paste the evidence into Claude, Cursor, or your coding agent with a prompt like this:

Next steps