Setup

Claude Desktop

Add it through Settings → Connectors:

1. Open Settings → Connectors
2. Click Add Connector
3. Enter the URL: https://mcp.whisper.security
4. Sign in with your Whisper Security account

Claude Code

claude mcp add --transport http whisper-graph https://mcp.whisper.security

Opens your browser for sign-in on first use. Scope options:

• --scope user -- all projects
• --scope project -- current project only
• --scope local -- this machine, this project (default)

Cursor

1. Open Settings → MCP
2. Click Add new global MCP server
3. Paste:

{
  "mcpServers": {
    "whisper-graph": {
      "url": "https://mcp.whisper.security"
    }
  }
}

4. Save and restart Cursor For team-wide config, use .cursor/mcp.json in the project root instead.

Create .vscode/mcp.json in your project root:

{
  "servers": {
    "whisper-graph": {
      "type": "http",
      "url": "https://mcp.whisper.security"
    }
  }
}

For user-level config (all projects), use Command Palette > MCP: Add Server.

Windsurf

1. Open Settings (Cmd+, on Mac, Ctrl+, on Windows)
2. Search for MCP
3. Click View raw config
4. Add:

{
  "mcpServers": {
    "whisper-graph": {
      "serverUrl": "https://mcp.whisper.security"
    }
  }
}

5. Save and restart Windsurf uses serverUrl instead of url.

Antigravity

1. Click ... at the top of the chat panel
2. Click MCP Servers > Manage MCP Servers > View raw config
3. Add to mcp_config.json:

{
  "mcpServers": {
    "whisper-graph": {
      "serverUrl": "https://mcp.whisper.security"
    }
  }
}

4. Go back to Manage MCP Servers and click refresh Config file: ~/.gemini/antigravity/mcp_config.json

ChatGPT

1. Go to chatgpt.com → Settings → Connectors
2. Click Add Connector
3. Enter the URL: https://mcp.whisper.security
4. Complete the sign-in ChatGPT supports OAuth only.

OpenAI Codex

Add to ~/.codex/config.toml:

[mcp_servers.whisper-graph]
url = "https://mcp.whisper.security"

Then authenticate:

codex mcp login whisper-graph

Other clients

Any MCP client that speaks Streamable HTTP works.

npx mcp-remote https://mcp.whisper.security

Connecting through API key

If your client doesn't support OAuth, you can authenticate with an API key instead.

1. Go to console.whisper.security and generate an API key
2. Pass it as a Bearer token in the Authorization header

Most MCP clients let you set custom headers in their config. Add:

Authorization: Bearer YOUR_API_KEY

For STDIO-only clients, use the mcp-remote bridge with the --header flag:

npx mcp-remote https://mcp.whisper.security --header "Authorization: Bearer YOUR_API_KEY"

Keep your API key out of version control.

Once the connector is registered, ask the assistant:

"List the WhisperGraph node labels."

The MCP client should invoke the list_labels tool and return roughly 20 labels (HOSTNAME, IPV4, IPV6, ASN, ANNOUNCED_PREFIX, FEED_SOURCE, …) with live counts. If you instead get an apology or a hand-written list of what the assistant thinks the schema looks like, the tool isn't connected — recheck the connector URL and re-authenticate.

• MCP Reference — every tool, resource, and prompt the connector exposes, plus example questions and the schema-introspection pattern AI agents should use before writing queries.
• Cypher API Reference — if you'd rather call the graph directly over REST without MCP.