Ext Ops Panel
Open dashboard
Comparison

SQL Server MCP vs SQL Server

SQL Server MCP is an MCP server published by cvelasquez. Marketplaces we read that list it: 1 (Official MCP Registry). SQL Server is an MCP server published by hlgurgel. 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
MarketplaceSQL Server MCPSQL Server
Official MCP Registry Listed
Version: 3.3.0
Downloads/month (npm): 674
Downloads/week (npm): 50
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.1.8
Downloads/month (PyPI): 967
Downloads/week (PyPI): 257
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

SQL Server MCP vs SQL Server
FactSQL Server MCPSQL Server
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-12Not published
Where it runs (differs)On your machine (@cevelas/mcp-sqlserver)On your machine (sqlserver-mcp-tools)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/cvelasquez/mcp-sqlservergithub.com/hlgurgel/mcp-sqlserver
Changes in the last 7 days (differs)20
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

SQL Server MCP

In its own words, on Official MCP Registry:

MCP server for DBAs running dozens of SQL Server instances: grouped connections, plans, indexes

SQL Server

In its own words, on Official MCP Registry:

Servidor MCP para SQL Server com controle de permissões e modo somente-leitura

How to run each

SQL Server MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "MSSQL_MCP_CONNECTIONS_JSON=<YOUR_MSSQL_MCP_CONNECTIONS_JSON>" --transport stdio mcp-sqlserver -- npx -y @cevelas/mcp-sqlserver

Requires: MSSQL_MCP_CONNECTIONS_JSON (secret)

SQL Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MSSQL_CONNECTION_STRING=<YOUR_MSSQL_CONNECTION_STRING>" --transport stdio sqlserver -- uvx sqlserver-mcp-tools

Requires: MSSQL_CONNECTION_STRING (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 SQL Server MCP asks for

  • MSSQL_MCP_CONNECTIONS
  • MSSQL_MCP_CONNECTIONS_JSON (secret)

Only SQL Server asks for

  • MSSQL_CONNECTION_STRING (secret)

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

What it can do: SQL Server MCP · What it can do: SQL Server · 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