mcp-knowledgebase
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | Yes | Database host address | |
| DB_NAME | Yes | Database name | |
| DB_PORT | No | Database port (default 3306) | |
| DB_USER | Yes | Database username | |
| DB_PASSWORD | Yes | Database password | |
| QUERY_TIMEOUT_MS | No | Query timeout in milliseconds | |
| MAX_ROWS_PER_PAGE | No | Maximum rows per page for pagination | |
| DB_CONNECTION_LIMIT | No | Maximum number of connections in pool |
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 |
|---|---|
| get_schemaA | Get the complete database schema for all tables. This includes table names, column names, data types, nullable status, defaults, and comments. Use this to understand the database structure before writing queries. Paginated to prevent token overflow. |
| get_keysA | Get all keys (primary, foreign, unique) for all tables. This helps understand table relationships for JOIN operations. Returns primary keys, foreign keys, unique keys, and a relationships map showing how tables connect. Paginated to prevent token overflow. |
| raw_queryA | Execute a raw SELECT query on the database. This tool provides read-only access with automatic pagination. The query is validated to ensure only SELECT statements are allowed. Results are paginated to prevent overwhelming responses. |
| describe_tableA | Get detailed information about a specific table including all columns, their types, keys, and comments. |
| get_tablesA | Get a list of all tables in the database with their metadata (type, comment, engine, row count). Paginated to prevent token overflow. |
| search_tablesA | Search for tables or columns by name pattern. Useful for finding specific tables or columns when you don't know the exact name. Paginated to prevent token overflow. |
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 6 tools
Tools mostly target distinct concerns: schema overview, keys, single-table details, table listing, search, and raw query. However, get_schema and describe_table overlap in providing column/key info, which could confuse an agent choosing between them. Overall boundaries are clear enough with careful reading.
Four tools use the get_ prefix (get_schema, get_keys, get_tables), but describe_table and search_tables use different verbs, and raw_query breaks the pattern entirely. The mix of get_, describe_, search_, and raw_ is readable but not consistent. A unified verb_noun convention would improve predictability.
Six tools is a well-scoped count for a database metadata and query server. Each tool covers a distinct aspect of exploration (schema, keys, tables, search, single-table details, raw queries), with no redundant tools. This is within the ideal range.
The toolset covers the main workflows: understanding schema, relationships, discovering tables, and running read-only queries. Minor gaps exist around indexes, views, or row sampling, but these are not critical for a knowledge base. The core surface is complete for navigation and querying.