Ext Ops Panel
Open dashboard
Comparison

io.github.cocaxcode/database-mcp vs io.github.rosch100/mcp-sqlite

io.github.cocaxcode/database-mcp is an MCP server published by cocaxcode. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.rosch100/mcp-sqlite is an MCP server published by rosch100. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
Marketplaceio.github.cocaxcode/database-mcpio.github.rosch100/mcp-sqlite
Official MCP Registry Listed
Version: 0.1.14
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.2.4
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

io.github.cocaxcode/database-mcp vs io.github.rosch100/mcp-sqlite
Factio.github.cocaxcode/database-mcpio.github.rosch100/mcp-sqlite
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@cocaxcode/database-mcp)On your machine (ghcr.io/rosch100/mcp-sqlite:0.2.4)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/cocaxcode/database-mcpgithub.com/rosch100/mcp-sqlite
Changes in the last 7 days00
First seen2026-10-112026-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

io.github.cocaxcode/database-mcp

In its own words, on Official MCP Registry:

MCP server for database connectivity. Multi-DB (PostgreSQL, MySQL, SQLite), 19 tools.

io.github.rosch100/mcp-sqlite

In its own words, on Official MCP Registry:

MCP server for SQLCipher 4 encrypted SQLite databases with full CRUD operations and query support

How to run each

io.github.cocaxcode/database-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio database-mcp -- npx -y @cocaxcode/database-mcp

io.github.rosch100/mcp-sqlite As a local MCP server: Docker image

Claude Code
claude mcp add --env "DB_PASSPHRASE=<YOUR_DB_PASSPHRASE>" --env "DB_PATH=<YOUR_DB_PATH>" --transport stdio mcp-sqlite -- docker run -i --rm -e DB_PASSPHRASE -e DB_PATH ghcr.io/rosch100/mcp-sqlite:0.2.4

Requires: DB_PASSPHRASE (secret), DB_PATH

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

The marketplaces of io.github.cocaxcode/database-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.cocaxcode/database-mcp · What it can do: io.github.rosch100/mcp-sqlite · 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 . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built