SQL Server vs io.github.rmterenzi/qseow-mcp
SQL Server is an MCP server published by hlgurgel. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.github.rmterenzi/qseow-mcp is an MCP server published by rmterenzi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.8 Downloads/month (PyPI): 967 Downloads/week (PyPI): 199 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.5.2 Downloads/month (npm): 129 Downloads/week (npm): 23 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.1.8 Downloads/month (PyPI): 967 Downloads/week (PyPI): 199 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
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
| Fact | SQL Server | io.github.rmterenzi/qseow-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 0 (worse) | 7 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (sqlserver-mcp-tools) | On your machine (qseow-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 10, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hlgurgel/mcp-sqlserver | github.com/rmterenzi/qseow-mcp |
| 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
SQL Server
Servidor MCP para SQL Server com controle de permissões e modo somente-leitura
io.github.rmterenzi/qseow-mcp
Agent tools for Qlik Sense Enterprise on Windows: troubleshoot, govern, query and build.
How to run each
SQL Server As a local MCP server: PyPI package
claude mcp add --env "MSSQL_CONNECTION_STRING=<YOUR_MSSQL_CONNECTION_STRING>" --transport stdio sqlserver -- uvx sqlserver-mcp-tools
Requires: MSSQL_CONNECTION_STRING (secret)
io.github.rmterenzi/qseow-mcp As a local MCP server: npm package
claude mcp add --env "QSEOW_HOST=<YOUR_QSEOW_HOST>" --env "QSEOW_JWT=<YOUR_QSEOW_JWT>" --transport stdio qseow-mcp -- npx -y qseow-mcp
Requires: QSEOW_HOST, QSEOW_JWT (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 asks for
MSSQL_CONNECTION_STRING (secret)
Only io.github.rmterenzi/qseow-mcp asks for
QSEOW_ALLOW_MUTATIONSQSEOW_AUTH_MODEQSEOW_CERT_KEY_PATHQSEOW_CERT_PATHQSEOW_HOSTQSEOW_JWT (secret)QSEOW_ROOT_CERT_PATHQSEOW_TLS_VERIFYQSEOW_TOOL_GROUPSQSEOW_VP_PREFIX
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: SQL Server · What it can do: io.github.rmterenzi/qseow-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.