marin1321/mcp-devtools

> **AI-native developer tools via Model Context Protocol.**
> A production-grade MCP server that gives AI agents (Claude, Cursor, Copilot, Continue, ...)
> safe, scoped access to your local development environment.
Why
The MCP ecosystem is full of single-purpose tutorials and vendor-locked
adapters. There is no well-maintained, multi-tool, framework-agnostic,
production-quality MCP package for everyday developer tooling.
mcp-devtools fills that gap with **14 tools**, **3 MCP Resources**,
**4 MCP Prompts**, a **Plugin API**, **two transport modes** (stdio + HTTP
with auth), and an **audit log** — built on patterns refined in production
at DailyBot.
Quick start
stdio (default)
Add it to **Claude Desktop** (~/Library/Application Support/Claude/claude_desktop_config.json):
Or **Cursor** (~/.cursor/mcp.json): same block.
HTTP transport
Create a mcp-devtools.json in your project root:
Then start the server:
The MCP endpoint will be available at http://localhost:3333.
Tools
| Group | Tools |
| ---------- | ---------------------------------------------------------------------------- |
| Filesystem | read_file, write_file, list_directory, search_files, get_file_info |
| Database | query_db, list_tables, describe_table |
| Process | run_command, read_logs, get_env, list_processes |
| OpenAPI | parse_openapi, call_api |
Per-tool reference: docs/tools/.
MCP Resources
The server exposes read-only data via MCP Resources:
| URI | Description |
| ------------------------ | -------------------------------------------- |
| devtools://tools | Catalog of all registered tools with schemas |
| devtools://server-info | Server version, transport, scope, tool count |
MCP Prompts
Curated prompt templates for common development workflows:
| Prompt | Description |
| ------------------- | ---------------------------------------------------------------- |
| debug_error | Systematically debug an error 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 |
Plugin API
Extend mcp-devtools with custom tools — no fork required.
**Config-based** (load at startup):
Each plugin module default-exports an array of tool definitions:
Configuration
Configuration is loaded by cosmiconfig
from mcp-devtools.json, .mcp-devtoolsrc, or the mcpDevtools key in
package.json. See mcp-devtools.example.json
and docs/configuration.md for the full schema.
Zero-config is supported: running npx @oscarmarin/mcp-devtools with no config uses
schema defaults (RNF-05).
Security
Four non-bypassable controls:
1. **Filesystem scope boundary.** Every path is resolved to an absolute and
compared against config.scope. Symlinks that escape scope throw
SCOPE_VIOLATION.
2. **Command allowlist.** run_command only executes binaries whose basename