Analytics Legends — SAP Analytics MCP Server

A read-only Model Context Protocol server over a curated corpus of the SAP analytics services market: who delivers SAP Datasphere, Business Data Cloud, SAP Analytics Cloud and BW/4HANA work, what the contract market looks like, what the day rates are, what the vocabulary means, and what has just happened.

It exists so that an assistant answering an SAP analytics question can cite a record instead of guessing. Every row carries a citation_url on analyticslegends.ai, and every response carries the size of the population it was drawn from.

Nothing to install. The server is hosted:

https://analyticslegends.ai/mcp        streamable-http

The public tools need no credential.

Connect

claude mcp add --transport http analytics-legends https://analyticslegends.ai/mcp
# with a subscriber key, to open the six gated tools:
claude mcp add --transport http analytics-legends https://analyticslegends.ai/mcp \
  --header "Authorization: Bearer alk_…"

{
  "mcpServers": {
    "analytics-legends": {
      "type": "streamable-http",
      "url": "https://analyticslegends.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "analytics-legends": {
      "type": "streamable-http",
      "url": "https://analyticslegends.ai/mcp",
      "headers": { "Authorization": "Bearer alk_…" }
    }
  }
}

The manifest is served at /.well-known/mcp.json and mirrored in this repository as mcp.json. tools/list is the authority for the surface — this README is a copy, and a copy can drift.

The 20 tools

Fourteen are public and unauthenticated. Six need a subscriber key; they are listed and refuse by name, never hidden — an agent can see what it is missing. Three open at Consultant, three at Legend, and the MCP Pass opens all six.

Every tool is annotated readOnlyHint: true. The server writes nothing, anywhere.

Two rules it holds itself to

A count is read at query time, and it comes with its population. Responses carry _meta.match_count (what your filters matched) and _meta.tranche_total_row_count (the whole tranche). Quote those rather than any number written in a description — including the ones in this file.

A citation says what it is. Every item carries citation_url and citation_scope. record means the URL is that item's own page; section_hub means this platform publishes no page for that item and the URL is the section index — say so, or cite the section, but do not present a hub URL as the item's page. News items also carry source_url for the upstream publisher: cite both.

What is deliberately not served, at any tier

• People. Individual professionals are held as initials only. No tool returns anyone's identity or contact details.
• The matchers. Opportunity-to-consultant scoring stays on the platform.
• SAP's own documentation. Not ours to restate — cite SAP.

Retrieval with attribution is permitted. Training-data use is not.

Subscriptions

The six gated tools open with an analyticslegends.ai subscription (Consultant or above), or with the MCP Pass (€39.90/month) — the machine-access subscription: this server's entire paid tranche, no web subscriber screens.

Where the source lives

The platform's application repository is private: it holds a paid corpus and personal data. This repository is the server's public face — its manifest, its registry descriptor, its client configuration and this documentation. The server itself answers at https://analyticslegends.ai/mcp, and the honest way to inspect it is to call tools/list against it.

Health, with its own timestamp: /api/mcp-health.json — read its generated_at rather than assuming a cadence.

Published in the official MCP registry as ai.analyticslegends/sap-analytics.

Licence

MIT for the contents of this repository. The licence does not grant rights over the data served by the endpoint, which stays under the platform's terms.