Ext Ops Panel
Open dashboard
Comparison

Query Forge vs SAP HANA CLI

Query Forge is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). SAP HANA CLI is an MCP server published by SAP-samples. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). 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
MarketplaceQuery ForgeSAP HANA CLI
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 4.202607.1
Downloads/month (npm): 7 503
Downloads/week (npm): 2 138
Forks (GitHub): 29
Stars (GitHub): 112
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 4
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

Query Forge vs SAP HANA CLI
FactQuery ForgeSAP HANA CLI
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)No figure on GitHub112
Forks (GitHub) (differs)No figure on GitHub29
Last releaseNot publishedNot published
Where it runs (differs)Remote server (query-forge-mcp.vercel.app/api/mcp)On your machine (hana-cli)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedApache-2.0
Repository (differs)Not statedgithub.com/sap-samples/hana-developer-cli-tool-example
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Query Forge

In its own words, on Official MCP Registry:

Enterprise SQL query optimizer and performance analyzer.

SAP HANA CLI

In its own words, on Official MCP Registry:

150+ SAP HANA database tools as MCP tools for AI assistants

How to run each

Query Forge As a remote MCP server

Claude Code
claude mcp add --transport sse query-forge https://query-forge-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: payment-signature header

SAP HANA CLI As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio hana-cli -- npx -y -p hana-cli hana-cli-mcp hana-cli

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

Neither one's marketplaces publish the settings it asks for.

What it can do: Query Forge · What it can do: SAP HANA CLI · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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