Ext Ops Panel
Open dashboard
Comparison

Kagi Search vs SearXNG

Kagi Search is an MCP server published by kagisearch. Marketplaces we read that list it: 1 (Docker MCP Catalog). SearXNG is a plugin bundle for AI coding tools published by 88plug. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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 SearchSearXNG
Docker MCP Catalog Listed
Version: sha256:c26439346cd6
Forks (GitHub): 49
Pulls (Docker Hub): 19 866
Stars (Docker Hub): 1
Stars (GitHub): 542
Not marked · First seen
Not listed
Community marketplace 88plug/claude-code-plugins Not listed Listed
Version: 2026.9.62
No figure published
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 SearXNG
FactKagi SearchSearXNG
Marketplaces that list it11
Stars (GitHub) (differs)542No figure on GitHub
Pulls (Docker Hub) (differs)19 866No figure on Docker Hub
Forks (GitHub) (differs)49No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/kagisearch)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)2Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Parts of the bundle (differs)Not a bundle1
Licence (differs)MITFSL-1.1-ALv2
Repository (differs)github.com/kagisearch/kagimcpgithub.com/88plug/searxng-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15

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.

SearXNG

In its own words, on Community GitHub marketplaces:

Fast, token-efficient MCP for SearXNG metasearch. Privacy-respecting search across 70+ engines with stdio + streamable-http transports, Docker, and optional rendered (Playwright) fetch for JS-heavy pages. Self-hostable. The underlying server is also usable independently of Claude Code via `uvx --from git+https://github.com/88plug/searxng-mcp searxng-mcp`.

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)

SearXNG As a Claude Code plugin

Claude Code
/plugin marketplace add 88plug/claude-code-plugins
/plugin install searxng@88plug

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

Tools each declares

The marketplaces of SearXNG 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 SearXNG asks for

  • SEARXNG_MCP_BASE_URL

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

What it can do: Kagi Search · What it can do: SearXNG · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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