Ext Ops Panel
Open dashboard
Comparison

Devart MCP Server for SQL Server (ADO.NET) vs SQL

Devart MCP Server for SQL Server (ADO.NET) is an MCP server published by devart.com. Marketplaces we read that list it: 1 (Official MCP Registry). SQL is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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
MarketplaceDevart MCP Server for SQL Server (ADO.NET)SQL
Official MCP Registry Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 189
Downloads/week (npm): 29
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

Devart MCP Server for SQL Server (ADO.NET) vs SQL
FactDevart MCP Server for SQL Server (ADO.NET)SQL
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (Devart.Mcp.SqlServer)On your machine (@abhishekmcp/sql)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)github.com/devart-ai-connectivity/devart-mcp-server-sqlservergithub.com/abhishekkumar2021/mcp-suite
Changes in the last 7 days (differs)02
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

Devart MCP Server for SQL Server (ADO.NET)

In its own words, on Official MCP Registry:

Schema-aware read/write access to SQL Server through Devart dotConnect ADO.NET data provider.

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

Devart MCP Server for SQL Server (ADO.NET)

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

Requires: DEVART_MCP_SQLSERVER_CONNECTION (secret)

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.

Tools each declares

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

Settings each asks for

Only Devart MCP Server for SQL Server (ADO.NET) asks for

  • DEVART_MCP_SQLSERVER_CONNECTION (secret)

Only SQL asks for

  • DB_CONN_default (secret)
  • DB_WRITABLE

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

What it can do: Devart MCP Server for SQL Server (ADO.NET) · 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