MCP ServerStreamable HTTP28 tools
Geolix MCP Server
Connect Claude, Cursor and other MCP clients straight to your Geolix data. Ask in plain language; the answers come from the same data the dashboard shows.
claude mcp add geolix --transport http https://api.geolix.ai/mcp \
--header "x-api-key: glx_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"- server url
- https://api.geolix.ai/mcp
- transport
- Streamable HTTP
- auth
- x-api-key header, the same key as the REST API
- tools
- 2818 read-only, 10 that change configuration; clients ask before running a write tool.
- clients
- Claude Code · Claude Desktop · Cursor · VS Code · Windsurf
Overview
MCP (Model Context Protocol) is the open protocol AI assistants use to call external tools. Once connected, your assistant can look up brand visibility, compare competitors, inspect citation sources and add monitored intents on your behalf. You just ask.
- Brand visibility — how often, how high and in what tone a brand appears across ChatGPT, Perplexity, Gemini and more
- Competitor comparison — visibility, share of voice and sentiment side by side, with the gap
- Source analysis — which domains and URLs the answers cite, and what kind of sites they are
- Raw records — individual question-and-answer records, filterable and exportable
Setup
Create an API key
Sign in at app.geolix.ai, open Settings → API keys, create a key and copy it. MCP and the REST API share the same kind of key.
Add the server to your client
Every client needs the same three things:
| Setting | Value |
|---|---|
| Server URL | https://api.geolix.ai/mcp |
| Transport | Streamable HTTP |
| Header | x-api-key: glx_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
Where to put them in each client is in the next section.
Ask
Once connected, just ask, for example: "How did our visibility in ChatGPT change over the last 30 days?" The assistant picks the tools, pulls the data and answers.
Client configuration
Claude Code
claude mcp add geolix --transport http https://api.geolix.ai/mcp \
--header "x-api-key: glx_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"Claude Desktop
Settings → Connectors → Add custom connector, paste the server URL; for authentication choose header and enter x-api-key.
Cursor
Settings → Tools & Integrations → MCP → Add Custom MCP, or edit .cursor/mcp.json:
{
"mcpServers": {
"geolix": {
"url": "https://api.geolix.ai/mcp",
"headers": { "x-api-key": "glx_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }
}
}
}VS Code (GitHub Copilot)
Create .vscode/mcp.json; keep the key in an environment variable rather than committing it:
{
"servers": {
"geolix": {
"type": "http",
"url": "https://api.geolix.ai/mcp",
"headers": { "x-api-key": "${env:GEOLIX_API_KEY}" }
}
}
}Windsurf
Settings → MCP → Add Server, enter the server URL and the x-api-key header.
What to ask
A few prompts that work as-is. The assistant translates them into calls from the tool list below.
- "How has our brand visibility changed over the past 30 days, and which platform dropped most?"
- "Which competitor has the highest share of voice in ChatGPT, and how far ahead are they?"
- "What are the ten most-cited URLs, and how many of them are ours?"
- "Add five more monitored intents for the topic \"enterprise SaaS procurement\"."
How it works
On connect the assistant fetches the tool list (name, parameters, whether it is read-only). For each question it picks tools, calls them with arguments, and the server queries the Geolix database and hands JSON back for the assistant to compose an answer.
The data is exactly what the dashboard shows: the MCP server and the REST API read the same database under the same permissions, with no extra model processing in between.
Permissions
18 of the 28 tools are read-only and only pull data; 10 change configuration (create brands, add intents, trigger or cancel runs and so on).
Write tools are annotated with readOnlyHint: false, archive-type tools also carry destructiveHint: true; clients that honour these hints ask for confirmation before running them.
Tools
Grouped by resource. The tool name is what the assistant calls.
Brands
| Tool | Access | Description |
|---|---|---|
list_brands | read | List brands |
get_brand | read | Brand details |
create_brand | write | Create a brand |
update_brand | write | Update a brand |
Projects & intents
| Tool | Access | Description |
|---|---|---|
list_projects | read | List projects |
get_project | read | Project details |
create_project | write | Create a project |
update_project | write | Update project settings |
list_queries | read | List monitored intents |
add_queries | write | Add monitored intents |
update_query | write | Update an intent |
archive_query | write | Archive an intent |
suggest_topics | read | AI-suggested topics to monitor |
suggest_queries | read | AI-suggested intents |
Runs
| Tool | Access | Description |
|---|---|---|
list_runs | read | List detection runs |
get_run | read | Run details and progress |
get_completion | read | Completion of the current window |
trigger_run | write | Trigger a run |
cancel_run | write | Cancel a run |
Board
| Tool | Access | Description |
|---|---|---|
get_board | read | Overview metrics |
get_board_sources | read | Citation sources |
get_source_detail | read | Detail for one source |
get_competitive_gap | read | Competitive gap |
get_by_intent | read | Metrics by intent |
get_chat_records | read | Raw question-and-answer records |
get_chat_facets | read | Filter facets for records |
export_chats | read | Export records |
Others
| Tool | Access | Description |
|---|---|---|
reanalyze_project | write | Re-aggregate a project's history |
Troubleshooting
401 unauthorized
- The key must include the full
glx_live_prefix, 41 characters in total - Check in app.geolix.ai settings that the key has not been revoked
403 forbidden
- Write tools need the owner or admin role
- An account that has not yet been granted access also gets a 403
Connection timeout
- Confirm the URL is
https://api.geolix.ai/mcpand the transport is Streamable HTTP, not SSE - Some clients default to a short timeout; raise it to 120 seconds for long queries