Ext Ops Panel
Open dashboard
Comparison

Kagi Search vs Backwork

Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). Backwork is an MCP server published by tylergibbs1. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-25. 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 SearchBackwork
Docker MCP Catalog Listed
Version: sha256:c26439346cd6
Forks (GitHub): 49
Pulls (Docker Hub): 20 145
Stars (Docker Hub): 1
Stars (GitHub): 547
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.1.6
Downloads/month (npm): 1 449
Downloads/week (npm): 754
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.1.6
Downloads/month (npm): 1 449
Downloads/week (npm): 754
Forks (GitHub): 0
Stars (GitHub): 1
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 Backwork
FactKagi SearchBackwork
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)547 (better)1 (worse)
Pulls (Docker Hub) (differs)20 145No figure on Docker Hub
Forks (GitHub) (differs)49 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/kagisearch)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)2Not published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/kagisearch/kagimcpgithub.com/tylergibbs1/backwork-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 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.

Backwork

In its own words, on Official MCP Registry:

Medicare and commercial payer policies, prior auth, claim risk, and medical codes from Backwork.

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)

Backwork As a remote MCP server

Claude Code
claude mcp add --transport http backwork-mcp https://backworkhealth.com/mcp

Requires: BACKWORK_API_KEY (secret)

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

Only Backwork has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Backwork publish no list of tools, so we do not compare tools.

Settings each asks for

Only Kagi Search asks for

  • KAGI_API_KEY (secret)
  • KAGI_SUMMARIZER_ENGINE

Only Backwork asks for

  • BACKWORK_API_BASE
  • BACKWORK_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Kagi Search · What it can do: Backwork · 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. Package data comes from the public npm registry (registry.npmjs.org). 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