pitchfork mcp
- Usage:
pitchfork mcp [-l --local]
Runs a Model Context Protocol (MCP) server over stdin/stdout
This command starts an MCP server that exposes pitchfork daemon management to AI assistants (Claude, Cursor, etc.) over stdin/stdout using JSON-RPC.
Typically used as a subprocess by an MCP-aware AI agent.
By default every daemon across all projects is exposed. Pass --local to expose only the daemons of the project in the current directory.
Examples:
# In claude_desktop_config.json or similar:
{
"mcpServers": {
"pitchfork": {
"command": "pitchfork",
"args": ["mcp"]
}
}
}
# Expose only the current project's daemons (e.g. per worktree):
{
"mcpServers": {
"pitchfork": {
"command": "pitchfork",
"args": ["mcp", "--local"]
}
}
}
Tools provided:
pitchfork_status List all daemons and their state
pitchfork_start Start a named daemon
pitchfork_stop Stop a named daemon
pitchfork_restart Restart a named daemon
pitchfork_logs Return recent log output for a daemon
Flags
-l --local— Only expose daemons from the current projectThe project is resolved from the current directory the same way short daemon IDs are: the nearest config file's namespace, falling back to 'global' when no config file is found. Tools refuse daemons outside it.
Aliases:
--project-h --help— Print help
