OmniSQL MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_connectionsB | List all available database connections |
| get_connection_infoB | Get detailed information about a specific database connection |
| execute_queryA | Execute a SQL query on a specific database connection (read-only queries) |
| write_queryC | Execute INSERT, UPDATE, or DELETE queries on a specific database connection |
| create_tableB | Create new tables in the database |
| alter_tableB | Modify existing table schema (add columns, rename tables, etc.) |
| drop_tableA | Remove a table from the database with safety confirmation |
| get_table_schemaB | Get schema information for a specific table |
| export_dataC | Export query results to various formats (CSV, JSON, etc.) |
| test_connectionB | Test connectivity to a database connection |
| get_database_statsA | Get statistics and information about a database |
| list_tablesB | List all tables in a database |
| append_insightA | Add a business insight or analysis note to the memo |
| list_insightsA | List all stored business insights and analysis notes |
| begin_transactionC | Start a new database transaction |
| commit_transactionB | Commit an active transaction |
| rollback_transactionB | Rollback an active transaction |
| execute_in_transactionB | Execute a query within an active transaction |
| explain_queryB | Get the execution plan for a SQL query |
| compare_schemasB | Compare schemas between two database connections |
| get_pool_statsB | Get connection pool statistics for a connection |
| get_ssh_tunnel_infoA | Get the SSH tunnel / jump host profile associated with a database connection, as configured in the DB client's workspace (network handler config). Secrets are redacted; use test_connection to verify the tunnel actually connects. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Most tools pair a clear resource with a distinct action, so connection listing, testing, schema inspection, and query execution are easy to separate. The main source of ambiguity is execute_query vs execute_in_transaction (and to a lesser degree write_query), though the descriptions do state read-only vs transactional context.
All tools use lowercase snake_case with a verb_noun pattern like list_connections, create_table, and commit_transaction. The few phrases like execute_in_transaction or get_ssh_tunnel_info still follow the convention and remain predictable.
22 tools is on the heavy side and falls into the 16-25 borderline range. The count is defensible for a broad SQL/connection-management server, but the diagnostic and insight tools make the surface feel larger than a typical focused MCP server.
The toolset covers the main database lifecycle: connections, read/write SQL, transaction control, table DDL, schema inspection, export, and query planning. Gaps such as creating/deleting connections or managing indexes/views are present, but the core workflows are well supported.