MCP Server

🔌 MCP Server

🔌 English · 한국어

Control CLITrigger from any MCP client (Claude Desktop, Claude Code) just by chatting with your AI — list projects, create and run tasks, and check status. CLITrigger exposes an HTTP MCP endpoint that any local or remote MCP client can connect to.

---

Connect

1. Keep CLITrigger running. The MCP endpoint lives inside the server, so it's available whenever the app (or clitrigger) is up. Quit the app and the tools stop responding.
2. Open the sidebar ⚙ → Settings → MCP. The card shows a ready-to-paste config with your server URL and access token already filled in — you don't need to know the port.
3. Register it in your MCP client:

Claude Code — run the one-line command from the card:

claude mcp add --transport http clitrigger http://localhost:3000/mcp --header "Authorization: Bearer <token>"

Claude Desktop — add the JSON block from the card via Settings → Connectors → add custom connector, or paste it into claude_desktop_config.json:

{
  "mcpServers": {
    "clitrigger": {
      "type": "http",
      "url": "http://localhost:3000/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

If your Claude Desktop version's config only accepts stdio servers, bridge it with mcp-remote:

{ "mcpServers": { "clitrigger": {
  "command": "npx",
  "args": ["mcp-remote", "http://localhost:3000/mcp", "--header", "Authorization: Bearer <token>"]
}}}

4. Ask your AI: "List my CLITrigger projects", or "Create a task 'fix the login bug' in the myapp project and run it."

This works the same for npm, desktop app, and remote (tunnel) users — the endpoint is part of the running server. For remote use, the config URL is simply your tunnel address instead of localhost.

---

Tools

Tool	What it does
list_projects	List all registered projects
create_project	Register a new project (name + local path)
create_todo	Create a TODO in a project
start_todo	Start a TODO (headless by default)
stop_todo	Stop a running TODO
get_project_status	Project execution status summary
get_todo_logs	A TODO's execution logs

Together these cover the headless task loop end to end — capture work and run it without opening the web UI. Interactive terminal sessions (live streaming I/O) are not exposed over MCP.

---

Access token

CLITrigger generates a token on first launch and stores it locally; the Settings → MCP card embeds the current token in the copy-paste config. Anyone who can reach the server and holds this token gets full API access — treat it like a password, and be mindful when exposing the server over a tunnel.