junior

This MCP server is a stdio-based wrapper for the Junior MCP integration. It translates MCP tool calls into Junior CLI commands, allowing you to manage tasks, schedules, hooks, and daemon status through a consistent MCP interface. The server exposes 18 tools across four categories: tasks (create, list, show, cancel, retry, delete, logs), schedules (create, list, pause, resume, remove), hooks (create, list, pause, resume, remove), and daemon (status). To use it, install the Junior MCP wrapper via npx as shown in the configuration, ensure Junior is installed and on your PATH, and run requests against the MCP endpoint configured in your project’s .mcp.json. Each tool maps to corresponding Junior CLI commands, enabling you to programmatically manage your automation workflows with familiar MCP semantics.

Prerequisites:

• Node.js and npm installed on your system (npx is included with npm).
• Junior installed and available on your PATH (per Junior's installation instructions).

Installation steps:

1. Install the MCP wrapper via npx as configured in your project’s .mcp.json:

# In your project directory
npx -y @jhostalek/junior-mcp

2. Ensure your project’s .mcp.json includes the junior server configuration:

{
  "mcpServers": {
    "junior": {
      "command": "npx",
      "args": ["-y", "@jhostalek/junior-mcp"]
    }
  }
}

3. Verify Junior is installed and accessible:

junior --version

4. Run the MCP server if you want to start it directly (depending on your setup):

# If you have a local dev environment script
node path/to/server.js

Note: The exact startup method may vary depending on your project’s orchestration. The key requirement is that the junior-mcp wrapper is installed and Junior CLI is available on PATH.

Tips and considerations:

• Ensure Junior is installed and accessible on the system PATH before starting the MCP server.
• The MCP wrapper relies on npx to fetch the @jhostalek/junior-mcp package; network access is required during initial setup.
• If you update Junior or the MCP wrapper, re-run installation to ensure compatibility.
• When using environments (CI/CD, containers), make sure PATH includes the location of the Junior CLI and that npm permissions allow npx to install the wrapper.
• Common issues: missing PATH to Junior CLI, outdated npx cache, or permission errors writing to node_modules. Clearing npm cache or reinstalling can help.
• You can override or extend behavior by adjusting your .mcp.json with additional server configurations as needed by your project.