Connect to a Hologres instance, get table metadata, query and analyze data.
Connect to a Hologres instance, get table metadata, query and analyze data. Exposed over MCP by the hologres mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Hologres MCP Server serves as a universal interface between AI Agents and Hologres databases. It enables seamless communication between AI Agents and Hologres, helping AI Agents retrieve Hologres database metadata and execute SQL operations.
Everything the assistant can do here goes through one of these:
execute_hg_select_sql — Execute a SELECT SQL query in Hologres databaseexecute_hg_select_sql_with_serverless — Execute a SELECT SQL query in Hologres database with serverless computingexecute_hg_dml_sql — Execute a DML (INSERT, UPDATE, DELETE) SQL query in Hologres databaseexecute_hg_ddl_sql — Execute a DDL (CREATE, ALTER, DROP, COMMENT ON) SQL query in Hologres databasegather_hg_table_statistics — Collect table statistics in Hologres databaseParameters — schema_name (string), table (string)get_hg_query_plan — Get query plan in Hologres databaseget_hg_execution_plan — Get execution plan in Hologres databasecall_hg_procedure — Invoke a procedure in Hologres databasecreate_hg_maxcompute_foreign_table — Create MaxCompute foreign tables in Hologres databaselist_hg_schemas — Lists all schemas in the current Hologres database, excluding system schemaslist_hg_tables_in_a_schema — Lists all tables in a specific schema, including their types (table, view, external table, partitioned table)Installation goes through your MCP client rather than a global install: point it at mode on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 5 environment variables: HOLOGRES_HOST, HOLOGRES_PORT, HOLOGRES_USER, HOLOGRES_PASSWORD, HOLOGRES_DATABASE. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Hologres's toolset — execute_hg_select_sql, execute_hg_select_sql_with_serverless, execute_hg_dml_sql and 11 more — is a fair guide to whether it matches your workflow.
This entry was verified against Hologres's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| execute_hg_select_sql | Execute a SELECT SQL query in Hologres database |
| execute_hg_select_sql_with_serverless | Execute a SELECT SQL query in Hologres database with serverless computing |
| execute_hg_dml_sql | Execute a DML (INSERT, UPDATE, DELETE) SQL query in Hologres database |
| execute_hg_ddl_sql | Execute a DDL (CREATE, ALTER, DROP, COMMENT ON) SQL query in Hologres database |
| gather_hg_table_statistics | Collect table statistics in Hologres database |
| Parameters | schema_name (string), table (string) |
| get_hg_query_plan | Get query plan in Hologres database |
| get_hg_execution_plan | Get execution plan in Hologres database |
| call_hg_procedure | Invoke a procedure in Hologres database |
| create_hg_maxcompute_foreign_table | Create MaxCompute foreign tables in Hologres database. |
| list_hg_schemas | Lists all schemas in the current Hologres database, excluding system schemas. |
| list_hg_tables_in_a_schema | Lists all tables in a specific schema, including their types (table, view, external table, partitioned table). |
| show_hg_table_ddl | Show the DDL script of a table, view, or external table in the Hologres database. |
| query_and_plotly_chart | Execute a SELECT SQL query and generate a chart (bar, line, scatter, pie, histogram, area). Returns query results and a base64-encoded PNG image. |
Use uvx mode
```json
{
"mcpServers": {
"hologres-mcp-server": {
"command": "uvx",
"args": [
"hologres-mcp-server"
],
"env": {
"HOLOGRES_HOST": "host",
"HOLOGRES_PORT": "port",
"HOLOGRES_USER": "access_id",
"HOLOGRES_PASSWORD": "access_key",
"HOLOGRES_DATABASE": "database"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| HOLOGRES_HOST | Endpoint or connection string the server talks to. | Optional |
| HOLOGRES_PORT | Configuration value read at startup. | Optional |
| HOLOGRES_USER | Configuration value read at startup. | Optional |
| HOLOGRES_PASSWORD | Configuration value read at startup. | Optional |
| HOLOGRES_DATABASE | Configuration value read at startup. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.