Quolens MCP · devREAD-ONLY

Ask Quolens from Claude Desktop or Cursor.

This host serves the Quolens Model Context Protocol endpoint. Every tool wraps our public analytics API — brands, prompts, share-of-answer, sentiment, citations — so an LLM can query your GEO visibility conversationally with your own key.

Add it to your client

First: mint an API key at dev.quolens.ai/dashboard/settings/mcp-api — the key starts with geo_sk_ and belongs to your org.

Claude Desktop

  1. Settings → Connectors → Add custom connector. Name: Quolens (dev). URL: https://devmcp.quolens.ai/mcp. Add a custom header: AuthorizationBearer geo_sk_…. Save and toggle it on.
  2. Or edit the config JSON directly (Settings → Developer → Edit Config):
    {
      "mcpServers": {
        "quolens-dev": {
          "url": "https://devmcp.quolens.ai/mcp",
          "headers": { "Authorization": "Bearer geo_sk_..." }
        }
      }
    }
  3. Restart Claude Desktop. The tools appear under the quolens-dev server.

Cursor

  1. Settings → MCP → Add new MCP server. Name: quolens-dev. Type: URL. URL: https://devmcp.quolens.ai/mcp. Header: Authorization: Bearer geo_sk_…. Save.

claude.ai (web)

The Custom Connectors UI here expects an OAuth 2.1 server — we don't speak OAuth yet on this endpoint (tracked, next round). For now use Claude Desktop or Cursor above.

Try it out — sample prompts

What you can ask

Tools are one-to-one with /api/public/v1/*. Every analytics tool takes a filters object whose brand_id comes from list_brands.

list_brands
get_brand
list_prompts
get_visibility
get_share_of_answer
get_grounding_split
get_competitors
get_sentiment
get_top_cited_domains
get_citation_hijack
get_search_queries
get_dashboard

Endpoints on this host