Comparison

Darwin RAG vs io.github.fieldcure/rag

Darwin RAG is an MCP server published by Brightdotdev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.fieldcure/rag is an MCP server published by fieldcure. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplace	Darwin RAG	io.github.fieldcure/rag
Official MCP Registry	Listed Version: 0.2.18 Downloads/month (PyPI): 310 Downloads/week (PyPI): 46 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen 2026-10-11	Listed Version: 2.5.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen 2026-10-11

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

Darwin RAG vs io.github.fieldcure/rag
Fact	Darwin RAG	io.github.fieldcure/rag
Marketplaces that list it	1	1
Stars (GitHub) (differs)	1 (better)	0 (worse)
Forks (GitHub)	0	0
Last release	Not published	Not published
Where it runs (differs)	On your machine (darwin-rag)	On your machine (FieldCure.Mcp.Rag)
Transport	stdio	stdio
Tools it declares	Not published	Not published
Environment variables it asks for (differs)	4, secrets among them: 3	5, secrets among them: 0
Licence	Not stated	Not stated
Repository (differs)	github.com/brightdotdev/darwin	github.com/fieldcure/fieldcure-mcp-rag
Changes in the last 7 days	0	0
First seen	2026-10-11	2026-10-11

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

Darwin RAG

In its own words, on Official MCP Registry:

Local-first RAG engine with MCP server for AI agent integration.

io.github.fieldcure/rag

In its own words, on Official MCP Registry:

MCP RAG server with hybrid search, multi-KB support, and AI-powered chunk contextualization.

How to run each

Darwin RAG As a local MCP server: PyPI package

Claude Code

claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio darwin-rag -- uvx darwin-rag mcp

Requires: ANTHROPIC_API_KEY (secret), GEMINI_API_KEY (secret), OPENAI_API_KEY (secret)

io.github.fieldcure/rag

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Darwin RAG asks for

DARWIN_BASE_DIR

Only io.github.fieldcure/rag asks for

GROQ_API_KEY
VOYAGE_API_KEY

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

What it can do: Darwin RAG · What it can do: io.github.fieldcure/rag · Compare two other plugins

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 2026-10-14. We publish no contact details for plugin publishers.