{
"mcpServers": {
"mcp-editor": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Port of Anthropic's file editing tools to an MCP server
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
MIT. View license →
Is it maintained?
Last commit 412 days ago. 8 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Monitor browser logs directly from Cursor and other MCP compatible IDEs.
MCP Security Weekly
Get CVE alerts and security updates for Mcp Editor and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This is a direct port of Anthropic's filesystem editing tools from their computer use demos to a TypeScript MCP server. It was written largely by Claude Sonnet 3.5 on Roo Cline (now Roo Code) with probably not quite enough direct supervision. I checked over the code and use this server every day, but there may be mistakes or AI weirdness.
I recommend using this server along with mcp-server-commands
Get the files on your computer. Run:
npm install
npm build
If you're using the Claude desktop app, paste this into your config under "mcpServers", and edit the path to match where you put mcp-editor:
{
"mcpServers":
... your existing servers ...
"mcp-editor": {
"command": "node",
"args": ["/absolute/path/to/mcp-editor/dist/server.js"]
}
}
}
If you're using MCP Installer, you just need to provide your LLM with the path on your disk to mcp-editor.