universal-dev-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | Port for the HTTP server (default: 3333). | |
| MCP_API_KEY | No | Optional API key for HTTP endpoint authentication. | |
| PROJECT_ROOT | Yes | Absolute path to the project root directory. | |
| ALLOWED_PORTS | No | Comma-separated list of allowed ports for dev servers (e.g., '3000,5173'). | |
| ALLOWED_COMMANDS | No | Comma-separated list of allowed shell commands (e.g., 'npm test,npm run lint,npm run build'). | |
| ALLOWED_WRITE_DIRS | No | Colon-separated list of directories where file writes are allowed (defaults to PROJECT_ROOT). |
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 |
|---|---|
| get_active_projectA | Shows which project is currently active — name, root path, package info, file count, and git branch. Use this to visually confirm which project the MCP server is connected to. |
| get_project_infoA | Get a full overview of the project: package.json metadata, npm scripts, dependencies, detected config files, and a two-level file tree. Always call this first when starting to work on a new project. |
| view_pageA | Fetch the HTML content and structure of a page on a running local dev server. Returns the page title, meta tags, script sources, and visible text. Optionally returns the full raw HTML. |
| check_portA | Check whether a dev server is currently running and responding on a given localhost port. Run this before view_page to confirm the server is up. |
| get_api_responseA | Make an HTTP request to an API endpoint on a local dev server and return the full response. Supports all standard HTTP methods and an optional JSON request body. Useful for testing REST APIs, checking response shapes, and verifying status codes. |
| read_fileA | Read the contents of a file in the project. Optionally limit output to a range of lines. Use list_files first if you are unsure of the file path. |
| edit_fileA | Write new content to a file, replacing it entirely. A timestamped backup is automatically created in .mcp-backups/ before any change. Use patch_file instead when making a small targeted change. |
| patch_fileA | Replace a specific string or block of code within a file without rewriting the whole file. The old_string must appear exactly once in the file. A backup is created automatically before the change is applied. |
| list_filesA | List the files and directories in the project as a tree. Use this to understand project structure before reading or editing files. |
| delete_fileA | Delete a file from the project. A backup is automatically created in .mcp-backups/ before deletion. Cannot delete directories. |
| move_fileA | Move or rename a file within the project. A backup of the original is created before the move. Cannot move directories. |
| run_commandA | Run an allowlisted shell command in the project root directory (or a subdirectory via |
| search_filesA | Search for a text string or regex pattern across all files in the project. Returns matching file paths, line numbers, and the matching lines. Optionally filter by file name glob (e.g. '*.ts'). Skips node_modules, hidden directories, and binary files. |
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 13 tools
Most tools have clearly distinct purposes, but get_active_project and get_project_info overlap somewhat in project metadata, and edit_file/patch_file share a write-to-file role. Descriptions help clarify boundaries, so confusion is unlikely.
All tool names follow a consistent verb_noun snake_case pattern (get_, view_, check_, read_, edit_, patch_, list_, delete_, move_, run_, search_). No mixed conventions or vague verbs.
13 tools is well-scoped for a dev server MCP, covering project inspection, file operations, server interaction, and command execution. Each tool has a distinct role and the count feels balanced.
The set covers most workflows (read, edit, patch, delete, move, list, search files; test server endpoints; run commands) but lacks a dedicated create_file tool. Starting the dev server is also not directly handled, though check_port implies it may be externally managed.