A core toolkit MCP server providing essential, efficient tools for AI agents (like Cline/Claude) to interact with your project files.

This Node.js server implements the Model Context Protocol (MCP) to provide a foundational set of filesystem tools, operating safely within a defined project root directory. It focuses on common operations needed by agents, including partial file reads.

• 🛡️ Secure & Convenient Project Root Focus:
  • All operations are strictly confined to the project root directory, preventing unauthorized access.
  • Uses relative paths from the project root, simplifying interactions for the AI.
• ⚡ Optimized & Consolidated Tools:
  • Most tools support batch operations (e.g., reading multiple files, deleting multiple items) in a single request.
  • Partial File Reads: The read_content tool supports reading specific line ranges, saving tokens and processing time for large files.
  • Designed to reduce AI-server round trips, minimizing token usage and latency compared to executing individual commands.
• 🚀 Easy Integration: Get started quickly using npx with minimal configuration.
• 🐳 Containerized Option: Also available as a Docker image for consistent deployment environments.
• ✅ Robust Validation: Uses Zod schemas to validate all incoming tool arguments.

The simplest and recommended way to use this server is via npx, configured directly in your MCP host environment (e.g., Roo/Cline's mcp_settings.json). This ensures you always use the latest version from npm without needing local installation or Docker.

Configure your MCP Host:

Modify your MCP host's settings (e.g., mcp_settings.json) to run the server using npx.

{
  "mcpServers": {
    "nexus-tools": {
      "command": "npx",
      "args": [
        "@shtse8/nexus-tools"
      ],
      "name": "NexusTools (npx)"
    }
  }
}

(Alternative) Using bunx:

If you prefer using Bun, you can use bunx instead:

{
  "mcpServers": {
    "nexus-tools": {
      "command": "bunx",
      "args": [
        "@shtse8/nexus-tools"
      ],
      "name": "NexusTools (bunx)"
    }
  }
}

That's it! Restart your MCP Host environment (if necessary) for the settings to take effect. Your AI agent can now use the NexusTools. The server automatically determines the project root based on where the host environment runs it (typically your open project folder).

Provides an essential, batch-capable toolset:

• 📁 Listing & Status: list_files, stat_items
• 📄 Content Manipulation: read_content (supports partial reads via start_line/end_line), write_content (incl. append)
• ✏️ Search & Replace: search_files (regex), replace_content
• ✨ Editing: edit_file (basic string edits with indentation preservation, diff preview, dry run - experimental)
• 🏗️ Directory Management: create_directories
• 🗑️ Deletion: delete_items (recursive)
• ↔️ Moving & Copying: move_items, copy_items

For users who prefer containerization or need a specific environment.

1. Ensure Docker is running.

2. Configure your MCP Host:

Modify your MCP host's settings to run the Docker container. Crucially, you must mount your project directory to /app inside the container.

{
  "mcpServers": {
    "nexus-tools": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-v",
        "/path/to/your/project:/app",
        "shtse8/nexus-tools:latest"
      ],
      "name": "NexusTools (Docker)"
    }
  }
}

Explanation:

• -v "/path/to/your/project:/app": Mounts your local project directory into the container at /app. The server inside the container will treat /app as its root. Remember to use the correct absolute path for your system.
• shtse8/nexus-tools:latest: Specifies the Docker image. Docker will pull it if needed.

3. Restart your MCP Host environment.

1. Clone: git clone <your-new-repo-url> (Replace with actual URL once created)
2. Install: cd nexus-tools && npm install
3. Build: npm run build
4. Configure MCP Host:

{
  "mcpServers": {
    "nexus-tools": {
      "command": "node",
      "args": ["/path/to/cloned/repo/nexus-tools/build/index.js"],
      "name": "NexusTools (Local Build)"
    }
  }
}

1. Clone the repository (once created).
2. Install dependencies: npm install
3. Build: npm run build (compiles TypeScript to build/)
4. Watch for changes: npm run watch (optional, recompiles on save)

This repository uses GitHub Actions (.github/workflows/publish.yml) to automatically:

1. Publish the package to npm on pushes to main.
2. Build and push a Docker image to Docker Hub on pushes to main.

Requires NPM_TOKEN, DOCKERHUB_USERNAME, and DOCKERHUB_TOKEN secrets configured in the GitHub repository settings.

Contributions are welcome! Please open an issue or submit a pull request.