mcp-devtools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABASE_URL | No | PostgreSQL/MySQL connection string for the default database connection. | |
| MCP_AUTH_TOKEN | No | Token for HTTP bearer authentication. Set auth.token to env:MCP_AUTH_TOKEN in config. |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echo_testA | Returns the provided message and a server-side ISO timestamp. Used to verify the MCP server pipeline end-to-end. |
| read_fileB | Read a text file inside the configured scope. Optionally restrict to a line range. |
| write_fileA | Write a file atomically inside the configured scope (writes to a temp file then renames). |
| list_directoryC | List directory entries inside the configured scope, with optional recursion and glob filtering. |
| search_filesC | Search for a pattern (literal or regex) across files inside the configured scope. |
| get_file_infoA | Return metadata (size, type, MIME, line count, symlink info) for a file or directory. |
| query_dbC | Execute a parameterized SQL query against a configured database connection. Read-only by default. |
| list_tablesC | List tables in a configured database connection. |
| describe_tableC | Return column metadata for a table in a configured database connection. |
| run_commandC | Spawn a process from the configured allowedCommands list. Captures stdout/stderr with caps and a timeout. |
| read_logsC | Read the tail of a configured log file with optional filter. |
| get_envC | Return environment variables (process env or .env file) with optional masking. |
| list_processesB | List running processes, optionally filtered by name or listening port. |
| parse_openapiB | Parse an OpenAPI spec and return a summary of operations. |
| call_apiC | Invoke an operation defined in an OpenAPI spec. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| debug_error | Systematically debug an error in your project using mcp-devtools tools |
| code_review | Review a file for bugs, security issues, and code quality |
| explore_codebase | Explore and understand a project's structure and conventions |
| refactor_function | Refactor a function for readability, performance, or testability |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| tool_catalog | List of all registered tools with their metadata and input schemas. |
| server_info | Server runtime information: version, transport, scope, tool count, and more. |
TDQS
Scored across 15 tools
Each tool targets a distinct operation: database metadata vs query, file read vs write vs listing vs search, process listing vs command execution, API calling vs spec parsing, etc. No two tools have overlapping purposes.
All tools follow a verb_noun pattern in snake_case (e.g., list_directory, read_file, query_db). The verbs vary but are appropriate for the action, and the naming is uniform throughout.
15 tools is slightly broad for a devtools server covering databases, files, processes, APIs, logs, and environment variables, but each tool has a clear role and the count is not excessive for a general-purpose utility server.
Core developer utilities are covered (file ops, database queries, command execution, API handling), but there are gaps like no process kill, no file editing, no HTTP utilities, and database is read-only. The set feels like a curated collection rather than a comprehensive toolkit.