Devtools MCP server
io.github.marin1321/mcp-devtools·v1.0.1·3 starsMCP server giving AI agents safe access to filesystem, databases, processes, and APIs.
3 stars44 downloads/wk
Reviews
Write oneNobody has reviewed Devtools yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Devtools tools (15, 3 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
call_apiInvoke an operation defined in an OpenAPI spec.
describe_tableReturn column metadata for a table in a configured database connection.
echo_testReturns the provided message and a server-side ISO timestamp. Used to verify the MCP server pipeline end-to-end.
get_envReturn environment variables (process env or .env file) with optional masking.
get_file_infoReturn metadata (size, type, MIME, line count, symlink info) for a file or directory.
list_directoryList directory entries inside the configured scope, with optional recursion and glob filtering.
list_processesList running processes, optionally filtered by name or listening port.
list_tablesList tables in a configured database connection.
parse_openapiParse an OpenAPI spec and return a summary of operations.
query_dbwrite actionExecute a parameterized SQL query against a configured database connection. Read-only by default.
read_fileRead a text file inside the configured scope. Optionally restrict to a line range.
read_logsRead the tail of a configured log file with optional filter.
run_commandwrite actionSpawn a process from the configured allowedCommands list. Captures stdout/stderr with caps and a timeout.
search_filesSearch for a pattern (literal or regex) across files inside the configured scope.
write_filewrite actionWrite a file atomically inside the configured scope (writes to a temp file then renames).
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 88 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Devtools compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,273 servers
- Tools
- 15
- the typical server has 7
- Tools that change things
- 20%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 3
- more than 80% of 28,534 servers
- Downloads a week
- 44
- more than 38% of 11,915 servers with a package
What its tools let an agent do: 12 read · 1 create · 1 change · 1 run or deploy
Install Devtools in Claude Code, Cursor or VS Code
Runs npx -y @oscarmarin/mcp-devtools on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-devtools -- npx -y @oscarmarin/mcp-devtools
What the publisher says
From the Devtools repository's README, as published. We do not edit it. Read it on GitHub
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)
npx @oscarmarin/mcp-devtoolsAdd it to Claude Desktop (~/Library/Application Support/Claude/claudedesktopconfig.json):
{
"mcpServers": {
"devtools": {
"command": "npx",
"args": ["-y", "@oscarmarin/mcp-devtools"]
}
}
}Or Cursor (~/.cursor/mcp.json): same block.
HTTP transport
Create a mcp-devtools.json in your project root:
{
"transport": "http",
"port": 3333,
"auth": {
"token": "env:MCP_AUTH_TOKEN"
}
}Then start the server:
npx @oscarmarin/mcp-devtoolsThe MCP endpoint will be available at http://localhost:3333.
Tools
Per-tool reference: docs/tools/.
MCP Resources
The server exposes read-only data via MCP Resources:
MCP Prompts
Curated prompt templates for common development workflows:
Plugin API
Extend mcp-devtools with custom tools — no fork required.
Config-based (load at startup):
{
"plugins": ["./my-tools.js", "@scope/mcp-plugin-foo"]
}Each plugin module default-exports an array of tool definitions:
import { defineTool } from "@oscarmarin/mcp-devtools";
import { z } from "zod";Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Devtools: common questions
- Is Devtools MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Devtools safety report
- How do I install Devtools?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Devtools need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Devtools maintained?
- The last commit was 124 days ago (2026-07-01). The latest release is v1.0.1.
- How does Devtools compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,273 servers); tools 15 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.