Mcp Devtools
Let your coding agent read/write files, query databases, run processes, and call APIs through one MCP server with guardrails instead of ad-hoc shell access.
Overview
mcp-devtools is an MCP server for the Build phase that gives AI agents guarded access to filesystem, databases, processes, and APIs.
What is this MCP server?
- Stdio MCP server (@oscarmarin/mcp-devtools) on npm, v1.0.1
- Unified safe access to filesystem, databases, processes, and HTTP APIs
- Designed for AI agents that need dev environment operations without wide-open shells
- Open-source on GitHub (marin1321/mcp-devtools)
- [object Object]
What problem does it solve?
Agents default to unsafe or inconsistent shell hacks when they need to touch files, DBs, or APIs on your machine.
Who is it for?
Indie devs who run MCP daily and want one server for repo, DB, process, and API tasks during active coding.
Skip if: Teams that forbid any agent filesystem or process access, or builders who only need a single SaaS API with a dedicated MCP.
What do I get? / Deliverables
After install, your agent can invoke structured MCP tools for dev operations instead of improvising terminal commands.
- Stdio MCP server wired into agent config
- Tool calls for filesystem, DB, process, and API operations
- Repeatable dev automation without raw shell sprawl
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the primary value is wiring agent workflows to local and remote dev surfaces during implementation. Agent-tooling fits MCP servers that extend what Claude Code, Cursor, and Codex can touch safely on a machine.
How it compares
Broad dev-environment MCP integration, not a browser-only or single-vendor cloud skill.
Common Questions / FAQ
Who is mcp-devtools for?
Solo and small-team builders using Claude Code, Cursor, or Codex who want MCP-shaped access to files, databases, processes, and APIs while coding.
When should I use mcp-devtools?
Use it during Build when the agent must inspect repos, run local commands, query a database, or call dev APIs through one registered MCP server.
How do I add mcp-devtools to my agent?
Install @oscarmarin/mcp-devtools from npm, add a stdio MCP entry in your agent config pointing at the package, restart the client, and scope permissions to the paths and credentials you trust.