{
  "markdown": "<!-- mcp-name: ai.analyticslegends/sap-analytics -->\n\n# Analytics Legends — SAP Analytics MCP Server\n\nA **read-only** [Model Context Protocol](https://modelcontextprotocol.io) server over a\ncurated corpus of the **SAP analytics services market**: who delivers SAP Datasphere,\nBusiness Data Cloud, SAP Analytics Cloud and BW/4HANA work, what the contract market\nlooks like, what the day rates are, what the vocabulary means, and what has just\nhappened.\n\nIt exists so that an assistant answering an SAP analytics question can **cite a record\ninstead of guessing**. Every row carries a `citation_url` on analyticslegends.ai, and\nevery response carries the size of the population it was drawn from.\n\n**Nothing to install.** The server is hosted:\n\n```\nhttps://analyticslegends.ai/mcp        streamable-http\n```\n\nThe public tools need no credential.\n\n---\n\n## Connect\n\n<details open>\n<summary><b>Claude Code</b></summary>\n\n```bash\nclaude mcp add --transport http analytics-legends https://analyticslegends.ai/mcp\n# with a subscriber key, to open the six gated tools:\nclaude mcp add --transport http analytics-legends https://analyticslegends.ai/mcp \\\n  --header \"Authorization: Bearer alk_…\"\n```\n</details>\n\n<details>\n<summary><b>Claude web, Desktop and mobile</b> (custom connector)</summary>\n\nAdd a custom connector pointing at `https://analyticslegends.ai/mcp`. The public tranche\nanswers immediately, with no credential.\n\nTo open the paid tranche, use the connector's **request-header authentication** and set\n`Authorization` to `Bearer alk_…`. The credential is entered once, by whoever adds the\nconnector, and is shared by that workspace — one key, one daily quota. There is no OAuth\nconsent flow to walk: this server's unit of access is a personal API key minted on an\nanalyticslegends.ai account, not a delegated identity.\n</details>\n\n<details>\n<summary><b>Claude Desktop / any client reading a JSON config</b></summary>\n\n```json\n{\n  \"mcpServers\": {\n    \"analytics-legends\": {\n      \"type\": \"streamable-http\",\n      \"url\": \"https://analyticslegends.ai/mcp\"\n    }\n  }\n}\n```\n</details>\n\n<details>\n<summary><b>With a subscriber key</b> (opens the six gated tools)</summary>\n\n```json\n{\n  \"mcpServers\": {\n    \"analytics-legends\": {\n      \"type\": \"streamable-http\",\n      \"url\": \"https://analyticslegends.ai/mcp\",\n      \"headers\": { \"Authorization\": \"Bearer alk_…\" }\n    }\n  }\n}\n```\n</details>\n\nThe manifest is served at\n[`/.well-known/mcp.json`](https://analyticslegends.ai/.well-known/mcp.json) and mirrored\nin this repository as [`mcp.json`](./mcp.json). `tools/list` is the authority for the\nsurface — this README is a copy, and a copy can drift.\n\n---\n\n## The 20 tools\n\n**Fourteen are public and unauthenticated.** Six need a subscriber key; they are\n**listed and refuse by name**, never hidden — an agent can see what it is missing.\nThree open at Consultant, three at Legend, and the MCP Pass opens all six.\n\n| Tool | Answers |\n|---|---|\n| `search_firms` | Which SAP analytics providers match a country, kind, free text |\n| `count_firms_by` | A counting question in one call, instead of a page of rows |\n| `get_firm` | One organisation from the published directory |\n| `list_firm_kinds` | The directory's breakdown by organisation kind, with live counts |\n| `find_opportunities` | The live contract and permanent-role radar |\n| `search_news` | The curated SAP analytics news corpus |\n| `search_concepts` | The concept encyclopaedia — the vocabulary of the stack |\n| `get_concept` | One concept: title, category, level, tags, editor's summary |\n| `list_studies` | The deep-research study editions and their metadata |\n| `get_day_rate_benchmark` | The public day-rate aggregate by country, stack, seniority |\n| `list_sap_modules` | The canonical SAP module/product taxonomy |\n| `list_freelance_platforms` | The CV/profile platforms a consultant can sign up on |\n| `find_academy_modules` | The Academy training catalogue, searchable by module |\n| `query_knowledge_graph` | A traversal of the learning knowledge graph |\n| 🔒 `get_concept_card` | The full encyclopaedia card — body, key points, cheat sheet |\n| 🔒 `get_study` | One study **body** |\n| 🔒 `get_academy_module` | One Academy module, in full |\n| 🔒 `find_sap_clients` | The SAP end-customer corpus — who *runs* SAP |\n| 🔒 `get_sap_client_profile` | One end-customer's SAP footprint and analytics estate |\n| 🔒 `get_firm_intel` | A firm's practice size, partner level, delivery flags |\n\nEvery tool is annotated `readOnlyHint: true`. The server writes nothing, anywhere.\n\n---\n\n## Two rules it holds itself to\n\n**A count is read at query time, and it comes with its population.** Responses carry\n`_meta.match_count` (what your filters matched) and `_meta.tranche_total_row_count` (the\nwhole tranche). Quote those rather than any number written in a description — including\nthe ones in this file.\n\n**A citation says what it is.** Every item carries `citation_url` **and**\n`citation_scope`. `record` means the URL is that item's own page; `section_hub` means\nthis platform publishes no page for that item and the URL is the section index — say so,\nor cite the section, but do not present a hub URL as the item's page. News items also\ncarry `source_url` for the upstream publisher: cite both.\n\n---\n\n## What is deliberately **not** served, at any tier\n\n- **People.** Individual professionals are held as initials only. No tool returns\n  anyone's identity or contact details.\n- **The matchers.** Opportunity-to-consultant scoring stays on the platform.\n- **SAP's own documentation.** Not ours to restate — cite SAP.\n\nRetrieval with attribution is permitted. **Training-data use is not.**\n\n---\n\n## Subscriptions\n\nThe six gated tools open with an\n[analyticslegends.ai](https://analyticslegends.ai/pricing/) subscription (Consultant or\nabove), or with the **MCP Pass** (€39.90/month) — the machine-access subscription: this\nserver's entire paid tranche, no web subscriber screens.\n\n---\n\n## Where the source lives\n\nThe platform's application repository is private: it holds a paid corpus and personal\ndata. **This repository is the server's public face** — its manifest, its registry\ndescriptor, its client configuration and this documentation. The server itself answers\nat `https://analyticslegends.ai/mcp`, and the honest way to inspect it is to call\n`tools/list` against it.\n\nHealth, with its own timestamp:\n[`/api/mcp-health.json`](https://analyticslegends.ai/api/mcp-health.json) — read its\n`generated_at` rather than assuming a cadence.\n\nPublished in the official MCP registry as **`ai.analyticslegends/sap-analytics`**.\n\n## Licence\n\n[MIT](./LICENSE) for the contents of this repository. The licence does not grant rights\nover the data served by the endpoint, which stays under the platform's terms.\n",
  "bytes": 6752,
  "sha": "060f20ad166729a84e66c1efe0e4d67b5f4cd7612af4d57cae6183d796071269",
  "repo_slug": "analyticslegends/analytics-legends-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_ai_analyticslegends_sap_analytics_9cc3c6dd/readme"
}