Ext Ops Panel
Open dashboard
Comparison

io.github.dataplat/dbatools-mcp-server vs io.github.rmterenzi/qseow-mcp

io.github.dataplat/dbatools-mcp-server is an MCP server published by dataplat. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
Marketplaceio.github.dataplat/dbatools-mcp-serverio.github.rmterenzi/qseow-mcp
Official MCP Registry Listed
Version: 0.5.0
Downloads/month (npm): 202
Downloads/week (npm): 16
Forks (GitHub): 1
Stars (GitHub): 6
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

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.dataplat/dbatools-mcp-server vs io.github.rmterenzi/qseow-mcp
Factio.github.dataplat/dbatools-mcp-serverio.github.rmterenzi/qseow-mcp
Marketplaces that list it11
Stars (GitHub) (differs)6 (worse)7 (better)
Forks (GitHub)11
Last releaseNot publishedNot published
Where it runs (differs)On your machine (dbatools-mcp-server)On your machine (qseow-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 010, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/dataplat/dbatools-mcp-servergithub.com/rmterenzi/qseow-mcp
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.dataplat/dbatools-mcp-server

In its own words, on Official MCP Registry:

MCP server for dbatools — exposes SQL Server management commands as MCP tools

io.github.rmterenzi/qseow-mcp

In its own words, on Official MCP Registry:

Agent tools for Qlik Sense Enterprise on Windows: troubleshoot, govern, query and build.

How to run each

io.github.dataplat/dbatools-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio dbatools-mcp-server -- npx -y dbatools-mcp-server

io.github.rmterenzi/qseow-mcp As a local MCP server: npm package

Claude Code
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 io.github.dataplat/dbatools-mcp-server asks for

  • COMMAND_TIMEOUT_SECONDS
  • DBATOOLS_SAFE_MODE
  • MAX_OUTPUT_ROWS
  • PWSH_EXE

Only io.github.rmterenzi/qseow-mcp asks for

  • QSEOW_ALLOW_MUTATIONS
  • QSEOW_AUTH_MODE
  • QSEOW_CERT_KEY_PATH
  • QSEOW_CERT_PATH
  • QSEOW_HOST
  • QSEOW_JWT (secret)
  • QSEOW_ROOT_CERT_PATH
  • QSEOW_TLS_VERIFY
  • QSEOW_TOOL_GROUPS
  • QSEOW_VP_PREFIX

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

What it can do: io.github.dataplat/dbatools-mcp-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. 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