Tests, migrations, linters, deployments — you describe the command once and the AI can trigger it, with a schema when it needs arguments. Paired with the multi-project list, that is what makes a change spanning three microservices a single conversation rather than three. Custom tools are opt-in and time-limited, which is the right default for something that shells out.
CTX: an MCP server plus a context generator, shipped as a single dependency-free binary. It gives an assistant filesystem access across the projects you list, and lets you turn your own commands into tools.
- Filesystem tools — read and write files, and text or regex search across the codebase with context lines
- Directory exploration with filtering by pattern, date, size and content
- PHP structure analysis: class hierarchy, interfaces and dependencies
- Custom tools defined in context.yaml — give a command an id, a description and an optional JSON-schema argument list, and the AI can run it
- Multi-project setup, so several microservices are visible in one session and a cross-cutting change spans them
- Context documents generated from files, git diffs, GitHub repositories and URLs into clean markdown, for copy-paste workflows
- Full JSON Schema for the config, so an assistant can write and edit it for you
The binary, installed with the shell or PowerShell script — no Node.js, no Python, no runtime. ctx mcp:config detects your OS and writes the client configuration, or add the ctx server command yourself, with -c and a path to pin it to one project. ctx init creates context.yaml. Custom tools are gated by MCP_CUSTOM_TOOLS_ENABLE, and a command's runtime is capped by MCP_TOOL_MAX_RUNTIME, which defaults to 30.
One command — curl -sSL https://raw.githubusercontent.com/context-hub/generator/main/download-latest.sh | sh