View on GitHub

MCP Dev Tools

File & Directory Operations for Autonomous AI Development

Download this project as a .zip file Download this project as a tar.gz file

🎯 START HERE

πŸ‘€ For You (User)

Immediate action: See quickstart.md to get started in 5 minutes


πŸ€– For Claude (Future Conversations)

⚠️ IMPORTANT: If you are Claude working on this project in a new conversation, READ FIRST:

πŸ“– working-with-claude.md ← START HERE

This file contains critical rules to follow, including:

Why? Previous conversations had issues because code wasn’t tested before being declared complete.


πŸ“š Complete Documentation

For Users

Document Purpose Time
quickstart.md Quick start guide 5 min
installation.md Complete installation guide 15 min
testing.md Testing and validation 20 min
migration.md Migration 1.0β†’1.2 10 min
security.md Security and audit 15 min

For Claude (Development)

Document Purpose Time
working-with-claude.md MANDATORY RULES ⭐ 10 min
build-fixes.md Applied build fixes 5 min
troubleshooting.md Problem resolution 10 min
lessons-learned.md Bug fix history 5 min

Technical Documentation

Document Purpose Time
README.md Complete technical docs 30 min
changelog.md Version history 10 min
index.md Documentation navigation 3 min

βœ… Current Project Status

Version: 1.2.0
Status: βœ… Production Ready
MCP Tools: 14 (7 file + 4 directory + 3 search)
Tests: Ready for 180+ tests
Build: βœ… Working without errors


πŸš€ Quick Actions

For Users

cd packages/dev-tools
npm install
npm run build
# Then configure Claude Desktop

For Claude in Development

# ALWAYS do this before declaring work complete:
npm run build
node validate.js
npm audit --production

🎯 Quick Navigation

Need to β†’ Check out


⚠️ Important Rules

For Claude Developing On This Project

  1. ALWAYS read working-with-claude.md first
  2. ALWAYS test npm run build before saying β€œdone”
  3. ALWAYS verify files exist with file_exists
  4. ALWAYS read the result in dist/ after compilation
  5. NEVER declare work complete without testing

For Users

  1. Always use absolute paths in Claude Desktop config
  2. Restart Claude Desktop completely after modifications
  3. Check logs in .logs/ if there are issues
  4. Use npm audit regularly for security

πŸ—οΈ Project Structure

packages/dev-tools/
β”œβ”€β”€ src/                      # TypeScript source code
β”‚   β”œβ”€β”€ tools/               # MCP tools (14)
β”‚   β”œβ”€β”€ utils/               # Utilities
β”‚   β”œβ”€β”€ types/               # TypeScript types
β”‚   └── server.ts            # Main MCP server
β”œβ”€β”€ dist/                    # Compiled code (generated)
β”œβ”€β”€ docs/                    # Complete documentation
β”œβ”€β”€ tests/                   # Unit tests (ready for 180+)
β”œβ”€β”€ scripts/                 # Automation scripts
β”œβ”€β”€ README.md                # Technical documentation
└── package.json             # npm configuration

πŸ’‘ What Makes This Project Unique

  1. First production-ready MCP package for file management
  2. Enterprise security: Path validation, backups, rate limiting
  3. 14 complete tools: Files + Directories + Search
  4. Exhaustive documentation: Complete English documentation
  5. Ready for comprehensive tests: Framework for 180+ tests
  6. Documented lessons learned: To avoid future errors

πŸŽ‰ Final Result

This package allows Claude to:

Without risking:


Next action:


Version 1.2.0 - October 19-21, 2025
Production Ready with 14 MCP tools