Analytics Legends — SAP Analytics Intelligence

What Analytics Legends — SAP Analytics Intelligence MCP server does

Analytics Legends — SAP Analytics Intelligence MCP server exposes a read-only knowledge source for the SAP analytics services market. Its corpus covers providers delivering SAP Datasphere, Business Data Cloud, SAP Analytics Cloud, and BW/4HANA work, along with contract opportunities, day-rate aggregates, SAP terminology, curated news, research studies, training content, and related company information.

The service is designed for answers that need evidence rather than unsupported estimates. Returned records include a citation_url and citation_scope. A record scope identifies the item’s own page, while section_hub indicates that the URL points to a section index because no individual page is published. News records also include an upstream source_url.

Every tool is marked read-only, and the service does not write data. It does not return individual professionals or their contact details, expose opportunity-to-consultant matching, or reproduce SAP’s own documentation. Retrieval with attribution is allowed; training-data use is not.

How it works

The hosted endpoint uses streamable HTTP at https://analyticslegends.ai/mcp. Fourteen tools are public and unauthenticated. Six gated tools remain visible in the tool listing but reject calls unless the request includes a subscriber key, allowing an agent to identify unavailable capabilities instead of treating them as absent.

Query responses provide _meta.match_count, representing the number of records matching the request, and _meta.tranche_total_row_count, representing the complete population for the applicable access tier. These values are query-time metadata and should be preferred over static counts in documentation.

The live manifest is available at /.well-known/mcp.json, and tools/list is the authoritative description of the available tool surface. The repository contains a mirrored manifest and client configuration, but those copies may become outdated.

Setup and configuration

Analytics Legends — SAP Analytics Intelligence MCP server requires no local installation. Add the hosted URL as a streamable-HTTP MCP connection. Public access needs no credential. To access the paid tranche, send an Authorization request header with a bearer value beginning with alk_….

Claude Code can register the endpoint with its HTTP transport. Claude web, Desktop, and mobile can use a custom connector; Claude Desktop and other clients that read MCP JSON configuration can use the endpoint URL and optional headers. The subscriber credential is a personal API key issued through an analyticslegends.ai account, not an OAuth delegated-identity flow. In a shared workspace, the configured key is shared and subject to one daily quota.

Paid access is available through an analyticslegends.ai subscription at Consultant level or above, or through the MCP Pass. The repository license is MIT, but that license does not grant rights to the data served by the endpoint.

Tools and capabilities

Public tools include:

• Search, count, and retrieve firms, including organisation kinds and live directory counts.
• Find contract and permanent opportunities.
• Search SAP analytics news and concepts, or retrieve a concept’s metadata.
• List research studies and obtain public day-rate benchmarks by country, stack, and seniority.
• List SAP modules, freelance platforms, and Academy modules.
• Traverse the learning knowledge graph.

Subscriber tools provide full concept cards, study bodies, complete Academy modules, SAP end-customer searches and profiles, and firm intelligence such as practice size, partner level, and delivery indicators.

Limitations and notes

The server is a market corpus, not SAP’s documentation and not a people directory. Individual professionals are represented only by initials, and no tool returns their identity or contact information. Consultant matching remains on the platform rather than through MCP.

Citations require careful interpretation: a section-hub URL should not be presented as an item-specific page. News should cite both the Analytics Legends record and its upstream publisher. Access tiers can change, so clients should inspect tools/list and query metadata rather than relying solely on this documentation.