tool-generatorLABSCO SUMMARY
Adding a tool means writing a JSON file, not writing Go.
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.
What it is
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.
What you get
- File utilities: read, write, move and delete files and directories
- Prompt-defined tools loaded from
custom_prompts/— each file needs adescriptionand apromptfield, and registers automatically - Two shipped examples:
tool-generator, which writes a tool description and prompt template from a query, andpalette, which suggests a colour palette for a given colour - Three transports selected at launch: stdio by default, or
-transport sse/-transport httpwith-port 8080 -prompts-pathpoints the server at a prompt directory outside the repository
Requirements
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.
Setup effort
One command — go install github.com/ad/mcp-project-helper@latest
USE CASES
01
Giving an assistant read and write access to one project
Launch it with the project directory in scope and let the file tools handle reads, writes and moves.
02
Turning a prompt you keep re-pasting into a tool
Write it once as a JSON file in the prompts directory; it becomes a callable tool on the next start.
03
Serving the same tools over the network
Start it with -transport http and a port instead of running it as a child process.
2 tools
Listed in project docs. Your client may show a different list.
paletteBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation. Tools load from the prompts/ and custom_prompts/ folders, so you can add your own; only tool-generator and palette are named. The promised file utilities are not individually documented.
Requires
go on PATH
Where it runs
All 3 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
go install github.com/ad/mcp-project-helper@latestMCP Clients
VS Code — binary
VS CODE — BINARY · JSON
{
"servers": {
"helper": {
"type": "stdio",
"command": "<YOUR_PATH_TO_PROJECT_HELPER>",
"args": [
"-transport",
"stdio"
]
}
}
}VS Code — Docker
VS CODE — DOCKER · JSON
{
"servers": {
"helper": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"danielapatin/mcp-project-helper:latest",
"-transport",
"stdio"
]
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"helper": {
"command": "<YOUR_PATH_TO_MCP_PROJECT_HELPER>",
"args": [
"-transport",
"stdio"
]
}
}
}
