Ext Ops Panel
Open dashboard
Comparison

Kagi Search vs Analytics Legends — SAP Analytics Intelligence

Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). Analytics Legends — SAP Analytics Intelligence is an MCP server published by analyticslegends.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceKagi SearchAnalytics Legends — SAP Analytics Intelligence
Docker MCP Catalog Listed
Version: sha256:c26439346cd6
Forks (GitHub): 49
Pulls (Docker Hub): 19 884
Stars (Docker Hub): 1
Stars (GitHub): 544
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.9
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Kagi Search vs Analytics Legends — SAP Analytics Intelligence
FactKagi SearchAnalytics Legends — SAP Analytics Intelligence
Marketplaces that list it11
Stars (GitHub) (differs)544 (better)0 (worse)
Pulls (Docker Hub) (differs)19 884No figure on Docker Hub
Forks (GitHub) (differs)49 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)On your machine (mcp/kagisearch)Remote server (analyticslegends.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/kagisearch/kagimcpgithub.com/analyticslegends/analytics-legends-mcp
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Kagi Search

In its own words, on Docker MCP Catalog:

The Official Model Context Protocol (MCP) server for Kagi Search & other tools.

Analytics Legends — SAP Analytics Intelligence

In its own words, on Official MCP Registry:

AI agent for SAP analytics: firms, day rates, contract radar, news, concepts, studies

How to run each

Kagi Search As a local MCP server: Docker image

Claude Code
claude mcp add --env "KAGI_API_KEY=<YOUR_KAGI_API_KEY>" --transport stdio kagisearch -- docker run -i --rm -e KAGI_API_KEY mcp/kagisearch

Requires: KAGI_API_KEY (secret)

Analytics Legends — SAP Analytics Intelligence As a remote MCP server

Claude Code
claude mcp add --transport http sap-analytics https://analyticslegends.ai/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Analytics Legends — SAP Analytics Intelligence has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Analytics Legends — SAP Analytics Intelligence publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Analytics Legends — SAP Analytics Intelligence publish no settings it asks for, so we do not compare settings.

What it can do: Kagi Search · What it can do: Analytics Legends — SAP Analytics Intelligence · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built