API & MCP server
Snorklee exposes your data read-only to your other tools: scripts, dashboards (Google Looker Studio, Excel…), and AI assistants (Claude, Cursor and any MCP client). Everything goes through a personal API key — never through your password.
Creating a key
In Integration → API & MCP: name the key (the tool that will use it), click Create a key, and copy it immediately — it will never be shown again; only its fingerprint is stored on our side. A key can be revoked in one click, effective immediately; you can have 10 active ones.
What a key can do: read your sites, AI visibility, citations, tracked questions and action center. What it cannot do: modify anything, or read data from a site you don't own.
The REST API
Add the Authorization: Bearer snk_… header to your requests:
GET /api/v1/sites
GET /api/v1/sites/{id}/geo/visibility
GET /api/v1/sites/{id}/geo/citations?limit=50
GET /api/v1/sites/{id}/geo/questions
GET /api/v1/sites/{id}/actions
Responses are JSON, { data, meta } envelope. Limit: 300 requests per hour per key.
The MCP server
The Model Context Protocol lets an AI assistant query your Snorklee data on your behalf (“what's my citation rate this month?”). Paste this configuration into Claude, Cursor or any MCP client, replacing snk_… with your key:
{
"mcpServers": {
"snorklee": {
"type": "http",
"url": "https://snorklee.com/mcp",
"headers": { "Authorization": "Bearer snk_…" }
}
}
}
The assistant then gets 5 tools: list_sites, get_ai_visibility, list_citations, list_questions, list_actions — all read-only.
Reporting
For a no-code report: every dashboard card has a CSV export button, and the global export (button at the top of the Analytics tab) downloads a complete ZIP, category by category — including AI visibility (08-ai-visibility/). These files import as-is into Google Looker Studio, Excel or any spreadsheet.
Sovereignty
The MCP server and the API are built and hosted by Snorklee, in the European Union, without any SDK or third-party service: your data goes through no intermediary.