every-db-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| db_queryA | Execute SQL queries against configured databases (MySQL, DM8, Oracle, GaussDB). Available databases:
Default database: mysql-dev Use 'db_query' for SELECT queries, 'db_execute' for INSERT/UPDATE/DELETE/DDL operations. |
| db_executeB | Execute INSERT/UPDATE/DELETE/DDL operations against configured databases. Respects per-database permissions. |
| db_list_databasesA | List all configured database connections and their permissions |
| db_test_connectionB | Test connectivity to a specific database |
| db_get_table_structureB | Get table structure (columns, indexes, constraints) for a specific table |
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 5 tools
Each tool has a distinct purpose: listing databases, testing connections, retrieving table structure, executing SELECT queries, and executing write/DDL operations. There is no overlap, and the descriptions clearly differentiate them.
All tools share the 'db_' prefix and mostly follow a verb_noun pattern (e.g., db_list_databases, db_test_connection). 'db_query' and 'db_execute' are less descriptive but still consistent in using verbs for actions.
Five tools cover the essential database operations (listing, testing, schema inspection, querying, and executing) without being excessive or insufficient. The scope is well-balanced for a database MCP server.
The tool set covers core CRUD and schema operations. Minor gaps exist (e.g., no tool for creating or dropping databases or managing users), but these are reasonable omissions given the focus on read-access and configured databases.