Hana MCP

Before configuring the server, collect the hostname, port, username, password, and optionally the default schema and database name (for multi-tenant MDC deployments). HANA Cloud typically uses port 443; on-premise MDC instances often use port 3NN13 where NN is the instance number.

Edit your claude_desktop_config.json (or equivalent MCP client config) to add the hana-mcp-server entry. The server runs via npx and requires no separate installation step.

{
  "mcpServers": {
    "HANA Database": {
      "command": "npx",
      "args": ["-y", "hana-mcp-server"],
      "env": {
        "HANA_HOST": "your-hana-host.hanacloud.ondemand.com",
        "HANA_PORT": "443",
        "HANA_USER": "your-username",
        "HANA_PASSWORD": "your-password",
        "HANA_SCHEMA": "YOUR_SCHEMA"
      }
    }
  }
}

For multi-tenant HANA (MDC), add HANA_DATABASE_NAME to specify the tenant. For on-premise instances with self-signed certificates, set HANA_VALIDATE_CERT to false.

{
  "HANA_DATABASE_NAME": "TENANT_NAME",
  "HANA_PORT": "30013",
  "HANA_SSL": "true",
  "HANA_VALIDATE_CERT": "false"
}

By default all write operations are disabled. To enable specific DML operations, add the corresponding environment variables. Only enable what your use case requires.

{
  "HANA_ALLOW_INSERT": "true",
  "HANA_ALLOW_UPDATE": "true",
  "HANA_ALLOW_DELETE": "false"
}

Fully restart Claude Desktop (or reload the MCP server in your client) and ask Claude to list the available schemas or verify the HANA connection. A successful response confirms the server is authenticated and connected.