Ext Ops Panel
Open dashboard
Comparison

OneDroid Engram vs SQL

OneDroid Engram is an MCP server published by onedroid.ai. Marketplaces we read that list it: 1 (Official MCP Registry). SQL is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceOneDroid EngramSQL
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 190
Downloads/week (npm): 35
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

OneDroid Engram vs SQL
FactOneDroid EngramSQL
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (engram.onedroid.ai/mcp)On your machine (@abhishekmcp/sql)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/abhishekkumar2021/mcp-suite
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 7 h ago, requires a keyno remote endpoint we check

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

OneDroid Engram

In its own words, on Official MCP Registry:

Versioned agent memory in your own Postgres: portable context, permissioned, audit trail.

SQL

In its own words, on Official MCP Registry:

Read-only SQL querying + schema introspection over Postgres & SQLite, with a gated write mode.

How to run each

OneDroid Engram As a remote MCP server

Claude Code
claude mcp add --transport http engram https://engram.onedroid.ai/mcp

SQL As a local MCP server: npm package

Claude Code
claude mcp add --env "DB_CONN_default=<YOUR_DB_CONN_DEFAULT>" --transport stdio sql -- npx -y @abhishekmcp/sql

Requires: DB_CONN_default (secret)

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

Only OneDroid Engram has a remote endpoint we check. How we check endpoints

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 OneDroid Engram publish no settings it asks for, so we do not compare settings.

What it can do: OneDroid Engram · What it can do: SQL · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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