Analytics Legends — SAP AI & Analytics MCP Server
A read-only Model Context Protocol server over a curated corpus of the SAP AI & analytics services market: who delivers SAP Business AI and Joule, Business Data Cloud, SAP Datasphere, 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.
Looking for an MCP server that connects to your own SAP system (BTP, CAP, UI5, Fiori, ABAP, Datasphere…)? This one serves market data, not your tenant — the catalogue of SAP MCP servers lists the official SAP, AWS and community servers, verified on their own pages.
Connect
claude mcp add --transport http analytics-legends https://analyticslegends.ai/mcp
# with a subscriber key, to open the eight gated tools:
claude mcp add --transport http analytics-legends https://analyticslegends.ai/mcp \
--header "Authorization: Bearer alk_…"
Add a custom connector pointing at https://analyticslegends.ai/mcp. The public tranche
answers immediately, with no credential.
To open the paid tranche, use the connector's request-header authentication and set
Authorization to Bearer alk_…. The credential is entered once, by whoever adds the
connector, and is shared by that workspace — one key, one daily quota. There is no OAuth
consent flow to walk: this server's unit of access is a personal API key minted on an
analyticslegends.ai account, not a delegated identity.
{
"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 22 tools
Fourteen are public and unauthenticated. Eight 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, five at Legend, and the MCP Pass opens all eight.
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 eight 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.