mcp-database
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | Yes | The database host (e.g., localhost) | |
| DB_NAME | Yes | The database name | |
| DB_PORT | No | The database port (default: 3306) | 3306 |
| DB_USER | Yes | The database user (e.g., readonly_user) | |
| MAX_ROWS | No | Maximum rows returned per query (default: 1000) | 1000 |
| DB_PASSWORD | Yes | The database password | |
| QUERY_TIMEOUT_MS | No | Query timeout in milliseconds (default: 15000) | 15000 |
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 |
|---|---|
| list_tablesA | Tampilkan daftar semua tabel di database. Gunakan ini lebih dulu untuk tahu tabel apa saja yang tersedia sebelum membuat query. |
| describe_tableA | Tampilkan struktur (kolom, tipe data, nullable, key) dari sebuah tabel. Gunakan untuk memahami skema sebelum menulis SELECT. |
| run_queryA | Jalankan query SQL read-only (SELECT/SHOW/DESCRIBE/EXPLAIN/WITH) untuk pengecekan data. Perintah tulis (INSERT/UPDATE/DELETE/DROP/dll) akan ditolak. Hasil dibatasi maksimal 1000 baris. |
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 3 tools
Each tool has a clear, distinct purpose: listing tables, describing table schema, and running custom queries. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (list_tables, describe_table, run_query), making them predictable.
Three tools is minimal but appropriate for a read-only database server, covering the essential operations. Slightly more could be added, but not necessary.
The set covers the core read-only operations: enumeration, schema inspection, and arbitrary queries. Minor gaps like listing views or indexes exist, but the surface is sufficient for most exploration tasks.