DevVault MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | No | Database connection URL. If not provided, it is read from the .env file specified by DEVVAULT_ENV_PATH or default ../devvault-backend/.env. | |
| DEVVAULT_ENV_PATH | No | Path to an .env file that may contain the DATABASE_URL. If not set, defaults to ../devvault-backend/.env. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| db_infoA | Show which database this server is connected to (host/db only, no credentials). |
| list_tablesA | List public tables with their live row estimates. |
| describe_tableA | Show columns (name, type, nullable, default) for a table. |
| count_rowsB | Exact row counts for the main DevVault tables. |
| run_queryA | Run a single read-only SQL statement (SELECT/WITH/EXPLAIN/SHOW). Executes inside a READ ONLY transaction. Use $1, $2… placeholders with params. |
| run_writeA | Run a single INSERT/UPDATE/DELETE. DDL (DROP/TRUNCATE/ALTER/…) and unscoped UPDATE/DELETE (no WHERE) are refused unless allowDangerous=true. Add "RETURNING *" to see affected rows. |
| seed_dummyA | Insert dummy rows (with valid cuid ids + timestamps) into snippets/bookmarks/notes/commands/prompts, attached to existing users. Great for filling the empty prompts/commands tables. Returns how many rows were inserted. |
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 7 tools
Most tools have distinct purposes: querying, writing, seeding, and introspection. However, run_query and run_write are clear opposites, and count_rows overlaps slightly with db_info/list_tables in terms of database introspection, though they serve different specific needs.
All tool names use a consistent verb_noun pattern: run_query, run_write, seed_dummy, db_info, list_tables, describe_table, count_rows. Each name clearly indicates the action and the target, making the set highly predictable.
With 7 tools, the count is well within the ideal range for a database management server. Each tool covers a core operation (query, write, seed, introspect), and none feel redundant. A couple more tools for advanced operations (e.g., transactions, backups) could be added, but the current count is appropriate.
The server covers essential database operations: querying, writing, seeding dummy data, and introspection (list tables, describe schema, row counts). It lacks tools for schema modification or data deletion scoped by ID, but the primary workflows for development (read, write, seed, introspect) are well covered.