The interesting part is the prompt directory: a new tool is a small JSON file with a description and a prompt, picked up on the next start, so extending the server does not mean touching the codebase or rebuilding. The file utilities are conventional and run with your own permissions — worth pointing at a specific project directory rather than a home folder.
A single Go binary that gives a client two things: file utilities for reading, writing, moving and deleting files and directories, and a mechanism for adding your own tools by dropping JSON prompt files into a directory. Each prompt file declares a description and a prompt, and the tool registers itself at startup.
- File utilities: read, write, move and delete files and directories
- Prompt-defined tools loaded from `custom_prompts/` — each file needs a `description` and a `prompt` field, and registers automatically
- Two shipped examples: `tool-generator`, which writes a tool description and prompt template from a query, and `palette`, which suggests a colour palette for a given colour
- Three transports selected at launch: stdio by default, or `-transport sse` / `-transport http` with `-port 8080`
- `-prompts-path` points the server at a prompt directory outside the repository
No account and no key. Install with `go install github.com/ad/mcp-project-helper@latest` — the binary lands in `$GOBIN` or `$HOME/go/bin`, which needs to be on your `$PATH` — or build from source with `make build-local`. A published Docker image, `danielapatin/mcp-project-helper:latest`, works for clients that prefer to launch a container. It reads and writes files with your permissions, so scope the working directory deliberately.
One command — go install github.com/ad/mcp-project-helper@latest