mcp-claude-code

This MCP server implements Claude Code-like capabilities, enabling Claude to inspect, modify, and manage a codebase through a rich set of file and project operations. It exposes tools for reading and writing files, performing precise text edits, and executing shell commands across supported languages. In addition to basic file I/O, the server provides advanced features such as recursive directory exploration, pattern search with ripgrep integration, AST-aware code search, notebook cell handling, and structured task/delegation workflows. Agents can be dispatched to work concurrently, allowing Claude to orchestrate complex multi-step tasks while maintaining proper permission and security checks.

Prerequisites:

• Node.js installed on your machine (version 14+ recommended)
• Access to the repository containing the MCP Claude Code server

Installation steps:

1. Clone the repository: git clone <repository-url>
2. Navigate to the project directory: cd mcp-claude-code
3. Install dependencies: npm install
4. Configure environment (examples):
   • In a .env file or your environment, set: MCP_LOG_LEVEL=info MCP_ALLOWED_ROOTS=/workspace MCP_MODEL_PROVIDER=<your-lite-llm-provider-config>
5. Start the MCP server: node server.js
6. Verify the server is running by sending a test MCP request or visiting the health endpoint (as documented in INSTALL.md).

If your setup uses a container or a different runtime, adapt the start command accordingly (see mcp_config in this document).

Notes and tips:

• Ensure the server’s allowed roots and permissions match your project layout to avoid permission errors during file operations.
• When using read/write/edit-related tools, prefer atomic operations (e.g., multi_edit) for large or critical changes to minimize partial updates.
• For large codebases, enable batch or dispatch_agent workflows to parallelize tasks and improve responsiveness.
• If you integrate with an external LLM provider, validate input sanitation and output handling to prevent unintended file modifications.
• Review the Security section in the README for recommended practices and potential caveats related to shell command execution and file system access.