HANA Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HANA_SSL | No | Enable SSL connection | true |
| HANA_HOST | Yes | HANA database hostname | |
| HANA_PORT | Yes | HANA database port | 443 |
| HANA_USER | Yes | Database username | |
| LOG_LEVEL | No | Logging level | info |
| HANA_SCHEMA | No | Default schema | |
| HANA_ENCRYPT | No | Enable encryption | true |
| HANA_PASSWORD | Yes | Database password | |
| HANA_VALIDATE_CERT | No | Validate SSL certificate | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hana_show_configB | Show the HANA database configuration |
| hana_test_connectionB | Test connection to HANA database |
| hana_list_schemasB | List all schemas in the HANA database |
| hana_show_env_varsB | Show all HANA-related environment variables (for debugging) |
| hana_list_tablesC | List all tables in a specific schema |
| hana_describe_tableC | Describe the structure of a specific table |
| hana_list_indexesC | List all indexes for a specific table |
| hana_describe_indexC | Describe the structure of a specific index |
| hana_execute_queryC | Execute a custom SQL query against the HANA database |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| hana_query_builder | Build a SQL query for HANA database |
| hana_schema_explorer | Explore HANA database schemas and tables |
| hana_connection_test | Test HANA database connection |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose targeting specific database operations like describing structures, listing resources, executing queries, or showing configuration. There is no overlap in functionality that would cause confusion between tools.
All tools follow a consistent 'hana_verb_noun' pattern with snake_case throughout, using clear verbs like describe, list, execute, show, and test. This predictable naming makes the tool set easy to navigate and understand.
With 9 tools, this server is well-scoped for database interaction, covering essential operations like connection testing, schema exploration, query execution, and configuration viewing. Each tool earns its place without feeling excessive or insufficient.
The tool set provides strong coverage for database exploration and querying, including CRUD-like operations via custom SQL. Minor gaps exist, such as no explicit tools for creating or modifying database objects, but agents can work around this using the execute_query tool for most needs.