Anydb MCP vs Hana MCP Server
A side-by-side look at the Anydb MCP and Hana MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Anydb MCP for databases work as a local process; choose Hana MCP Server for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Anydb MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
db_list, db_query, db_schema.
Choose Hana MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
HANA_HOST, HANA_PORT, HANA_USER, HANA_PASSWORD, HANA_SCHEMA. - You want tools like
hana_show_config, hana_test_connection, hana_list_schemas.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 59/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Free | Free |
| Required env vars | None listed | HANA_HOSTHANA_PORTHANA_USERHANA_PASSWORDHANA_SCHEMA |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 72 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 5 | 34 |
| Full listing | View Anydb MCP | View Hana MCP Server |
Tools & capabilities
Anydb MCP tools 5
db_listList the connection profiles from the anydb config file (~/.anydb/db.json): name, description, driver, which one is the default, and whether it is read-only. Call this first whenever you do not already know a profile name, then pass the name to the other tools as "profile". The result never contains a connection string, a host, a username or a password -- not masked, absent -- because this text goes into your context window and a config file is writable by anyone who can write files. If there is no config file, use "uri" with the other tools instead.db_queryRun one statement against one database (PostgreSQL, MySQL/MariaDB, SQLite, MongoDB or Redis, inferred from the connection). READ-ONLY BY DEFAULT: writes are refused unless "readOnly" is false, and statements that change schema or privileges additionally require "allowDestructive" to be true. Call db_list and db_schema first so table and column names are not guessed, and prefer "params" over inlining values in "query" so the values never appear in the statement text. Put a LIMIT in every query: results are capped anyway, and a cap you did not ask for is how a table gets silently half-read. MongoDB: "collection" is required and "action" picks the operation -- find, count, distinct, aggregate and explain read; insert, update, updateOne, replace, delete and deleteOne write and need "readOnly": false. Prefer the *One actions: one document, not every match. Redis: "query" is a single command such as GET or SCAN.db_schemaDescribe the structure of a database: tables and their columns for SQL, collections with their indexes for MongoDB, keyspace statistics for Redis. Call it before writing a query so names are not guessed -- it is almost always cheaper than a failed query. Runs read-only introspection statements only, never a statement of yours, and "table"/"collection" are bound as parameters wherever the driver allows rather than pasted into SQL. "detail": "full" adds foreign keys, index definitions, primary and unique constraints, row estimates, and inferred field schemas for MongoDB.db_explainReturn the execution plan for a statement WITHOUT running it. Read-only by construction: the statement is planned and not executed, so this is the safe way to catch a sequential scan over a large table and the cheapest way to find a missing index. ANALYZE variants are refused here on purpose, because "EXPLAIN ANALYZE" runs the statement it plans. MongoDB: pass "collection" and a find filter as "query"; a pipeline cannot be explained, use db_query action "aggregate" with a small limit. Redis has no plans, so this tool refuses it.db_healthAsk the database about itself: reachable or not, server version, the role this server authenticated as, whether that role or the server is read-only, object counts, and this server's pool and cache state. Use it instead of guessing at why a connection or a write failed. Note what "readOnly": false does and does not do: it is a request to THIS server, not a security boundary. The boundary is the database role -- a role holding INSERT will succeed whatever these flags say, and a role without them will fail however many are set.
Hana MCP Server tools 34
hana_show_configShow the HANA database configurationhana_test_connectionTest connection to HANA databasehana_list_schemasList schemas in the HANA database with optional prefix filter and pagination (HANA_LIST_DEFAULT_LIMIT / offset).hana_show_env_varsShow all HANA-related environment variables (for debugging)hana_list_tablesList tables in a schema with optional name prefix and pagination (HANA_LIST_DEFAULT_LIMIT / offset).hana_describe_tableDescribe the structure of a specific tablehana_explain_tableReturn column metadata merged with optional business semantics from HANA_SEMANTICS_PATH or HANA_SEMANTICS_URL (JSON keys: SCHEMA.TABLE or DB.SCHEMA.TABLE when catalog_database is set). Optional catalog_database reads SYS.* from another MDC database (e.g. HSP).hana_list_indexesList all indexes for a specific tablehana_describe_indexDescribe the structure of a specific indexhana_execute_queryExecute SQL against HANA. When HANA_QUERY_LIMITS_ENABLED=true, SELECT/WITH queries are wrapped with LIMIT/OFFSET (HANA_MAX_RESULT_ROWS) and row/column/cell caps apply; results are returned as-is otherwise. INSERT/UPDATE/DELETE are blocked by default; set HANA_ALLOW_INSERT, HANA_ALLOW_UPDATE, HANA_ALLOW_DELETE=true individually to permit each. Use limit, offset, maxRows, includeTotal as needed. If truncated, snapshotId may be returned for hana_query_next_page.hana_query_next_pageFetch the next page of a truncated SELECT using snapshotId from a previous hana_execute_query result (same SQL and parameters; TTL HANA_QUERY_SNAPSHOT_TTL_MS).hana_list_constraintsList primary key, unique, check, and foreign key constraints for a table (SYS.CONSTRAINTS + SYS.REFERENTIAL_CONSTRAINTS).- +22 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Anydb MCP
{
"mcpServers": {
"anydb-mcp": {
"command": "npx",
"args": [
"-y",
"anydb-mcp"
]
}
}
}
Hana MCP Server
{
"mcpServers": {
"hana-mcp-server": {
"command": "npx",
"args": [
"-y",
"hana-mcp-ui"
],
"env": {
"HANA_HOST": "YOUR_HANA_HOST_HERE",
"HANA_PORT": "YOUR_HANA_PORT_HERE",
"HANA_USER": "YOUR_HANA_USER_HERE",
"HANA_PASSWORD": "YOUR_HANA_PASSWORD_HERE",
"HANA_SCHEMA": "YOUR_HANA_SCHEMA_HERE"
}
}
}
}
Frequently asked questions
Anydb MCP is categorized under Databases and uses a local stdio subprocess. Hana MCP Server belongs to Databases and uses a local stdio subprocess. Pick Anydb MCP for databases work and Hana MCP Server for databases.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Anydb MCP is listed as free. Hana MCP Server is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add anydb-mcp and hana-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Anydb MCP has a quality signal of 59/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Hana MCP Server has 69/100 (Great) with 4 views, 0 installs and 72 GitHub stars.