MCP Setup

Connect Claude Desktop, Cursor, or any MCP client to your Clauge.

Clauge ships a built-in MCP server with 51 tools across the workspace tree, boards, cards, notes, meetings, REST collections, and coworker coordination. The server auto-starts on app launch — no flag, no separate process to manage.

Default endpoints

• HTTP — http://localhost:7421/mcp
• stdio — pipe directly to the Clauge binary with clauge mcp serve --stdio

From Claude Desktop

Add the following to your claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "clauge": {
      "command": "clauge",
      "args": ["mcp", "serve", "--stdio"]
    }
  }
}

Restart Claude Desktop. You'll see "clauge" under the MCP tools indicator.

From Cursor / Cline / Continue

Point the client at http://localhost:7421/mcp. The agent can now list boards, create cards, append notes, read meetings, raise PRs, manage REST collections, and call coworkers — all from inside its own UI.

Tool prefixes

Tools are namespaced: workspaces_*, boards_*, cards_*, notes_*, meetings_*, rest_collection_*, coworkers_*, workspace_*, activity_feed. One worth knowing about: cards_call_coworker — the agent in your terminal can @-mention a coworker on a card, and the coworker picks it up just like a human assignee.

The workspace tree

Clauge's model is Group › Project (see Workspace), and the MCP surface mirrors it:

• workspaces_list returns the whole tree nested — { groups: [{ id, name, projects: [{ id, name, repoUrl, linked, projectPath }] }] }, Personal first. Notes, boards and automations can hang off either level, so this is the call that tells you which workspaceId (a project) or groupId to pass elsewhere. There's nothing to paginate; limit/offset are accepted and ignored.
• linked is false when a project has no local folder bound. projectPath is that folder — cd there before doing code work.
• workspaces_upsert_for_project is lookup only, despite the name: it resolves a folder to the project that owns it and never creates one. Projects live inside groups and are created by the user in Clauge (Workspace › group › New project). An unlinked folder comes back as no_project: … — stop there and ask the user to create the project and link the folder. The path is canonicalised first (symlinks resolved, worktrees resolved to the parent repo, git remote as a fallback), so passing your shell's cwd works even from inside a worktree.

Cards with no code behind them

A card on a group board has no repository, and a card on an unlinked project has no checkout. The code tools (cards_start_work, cards_commit, cards_raise_pr, cards_push_to_repo, cards_link_pr, cards_check_pr_state, cards_claim) refuse those with group_board_no_code or project_unlinked. Both are terminal: move the card to a project board, or ask the user to link the folder. Chat, comments, notes and column moves work either way, and cards_call_coworker still runs — on a group board the coworker works in the group's own scratch directory.

Meetings

meetings_list, meetings_read and meetings_search read recorded meetings. Meetings are filed on a group or on a project, so meetings_list filters by groupId, workspaceId, or ungrouped: true. meetings_read returns the AI-generated notesMd summary by default — a full transcript runs to tens of thousands of tokens, so pass includeTranscript: true only when the notes genuinely don't answer the question. meetings_search covers titles, notes and transcripts, which is how you find "the meeting where we discussed X" rather than one named X.