mcp -developer-tool

This MCP server is a modular Go implementation of the Model Context Protocol. It exposes a pluggable set of tools under internal/tools, enabling secure file operations, shell command execution, and file inspection within configurable boundaries. The server is designed to restrict file operations to approved directories and to provide a straightforward mechanism to add new tools by implementing the Tool interface and registering them in the main server entry point. Use the built server to manage model-context based workflows where clients can query, read, write, or search files in a controlled environment guided by the server configuration.

Prerequisites:

• Go 1.18+ (or newer)
• GOPATH configured (optional if using modules)

Install and run:

1. Ensure you have Go installed and your environment set up.
2. Navigate to the repository root containing the mcp-server module.
3. Build and run the server:

# Build the server (or run directly with go run as shown below)
cd cmd/mcp-server
go build -o mcp-server

# Run the server
./mcp-server

If you prefer to run it without building a binary first, you can execute:

cd cmd/mcp-server
go run .

Optional: set environment variables to constrain paths before starting the server, e.g.:

export MCP_ALLOWED_PATHS=/home/user/safe:/tmp/workspace
export MCP_DENIED_PATHS=/home/user/.ssh:/home/user/credentials
./mcp-server

Notes and tips:

• The server enforces a path restriction system to limit file operations to allowed directories. Default behavior allows the current working directory unless overridden by MCP_ALLOWED_PATHS. Common sensitive directories such as .git and .env are denied by default.
• You can configure tools at runtime or extend the tooling by adding new files under internal/tools and registering them in the main server entry. Tools implement the Tool interface and can optionally implement ConfigAware to access server configuration for security checks.
• For shell-related tools (execute_shell_command), commands are whitelisted and must be executed within allowed paths to prevent unauthorized access.
• To test, run go test ./... from the repository root after ensuring dependencies are fetched. The internal server tests live under internal/server and can help validate behavior.
• If you modify configuration, restart the server to apply changes.