Ext Ops Panel
Open dashboard
Comparison

DBHawk vs Sezzlee SQL Server

DBHawk is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.

DBHawk is a plugin bundle for AI coding tools published by Datasparc. No marketplace we read lists it any more. Sezzlee SQL Server is an MCP server published by sezzlee. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceDBHawkSezzlee SQL Server
Community marketplace datasparc/dbhawk-mcp-plugin Removed on 2026-10-15
Version: 0.4.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
Downloads/month (npm): 500
Downloads/week (npm): 200
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

DBHawk vs Sezzlee SQL Server
FactDBHawkno longer listed · Sezzlee SQL Server
Marketplaces that list it (differs)01
Stars (GitHub) (differs)01
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@sezzlee/mssql-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 19, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/datasparc/dbhawk-mcp-plugingithub.com/sezzlee/mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-10-12

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of DBHawk

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • dbhawk com.datasparc/dbhawk

    Secure access to DBHawk datasources: browse schemas, run governed queries, DBHawk AI text-to-SQL.

    by datasparc.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • AI for Database

    Ask your databases questions in plain English, run read-only SQL and set up data alerts.

    by aifordatabase.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Dataassist-IO io.github.DataAssistIO/Dataassist-IO

    Query your org's data in natural language — read-only MCP access to SQL, NoSQL, files & warehouses.

    by DataAssistIO · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • QueryBear

    Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.

    by spencerpauly · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • DBHub

    Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite

    by bytebase · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • Databasin

    Explore Databasin data, run read-only queries, and manage your support tickets with secure sign-in.

    by Databasin-AI · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

DBHawk

In its own words, on Community GitHub marketplaces:

Read-only DBHawk datasource exploration + HawkAI over the /api/v2/mcp API.

Sezzlee SQL Server

In its own words, on Official MCP Registry:

Explore and query Microsoft SQL Server read-only: catalogue search, schema and bounded queries.

How to run each

DBHawk

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

Sezzlee SQL Server As a local MCP server: npm package

Claude Code
claude mcp add --env "SEZZLEE_MSSQL_DATABASE=<YOUR_SEZZLEE_MSSQL_DATABASE>" --env "SEZZLEE_MSSQL_PASSWORD=<YOUR_SEZZLEE_MSSQL_PASSWORD>" --env "SEZZLEE_MSSQL_SERVER=<YOUR_SEZZLEE_MSSQL_SERVER>" --env "SEZZLEE_MSSQL_USER=<YOUR_SEZZLEE_MSSQL_USER>" --transport stdio mssql -- npx -y @sezzlee/mssql-mcp

Requires: SEZZLEE_MSSQL_DATABASE, SEZZLEE_MSSQL_PASSWORD (secret), SEZZLEE_MSSQL_SERVER, SEZZLEE_MSSQL_USER

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 DBHawk asks for

  • DBHAWK_BASE_URL
  • DBHAWK_DEFAULT_DATASOURCE
  • DBHAWK_TOKEN (secret)

Only Sezzlee SQL Server asks for

  • SEZZLEE_MSSQL_CONNECT_TIMEOUT_MS
  • SEZZLEE_MSSQL_DATABASE
  • SEZZLEE_MSSQL_ENCRYPT
  • SEZZLEE_MSSQL_PASSWORD (secret)
  • SEZZLEE_MSSQL_PORT
  • SEZZLEE_MSSQL_QUERY_TIMEOUT_MS
  • SEZZLEE_MSSQL_SERVER
  • SEZZLEE_MSSQL_TRUST_SERVER_CERTIFICATE
  • SEZZLEE_MSSQL_USER

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

What it can do: DBHawk · What it can do: Sezzlee SQL Server · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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