Agents
MCP — connect your own coding agent
MCP connects the coding agent you already use — Claude Code, Cursor, and others — to the workspace. One connection per machine, and the to-dos assigned to you, the topics that asked for them, and what each topic has decided are all available where you work. It is one server for every tool; only the way you connect differs.
Connect it
Open the connect page
Click the laptop icon in the top bar (Agents & MCP) → the MCP tab.Pick your coding agent
Choose your tool from the dropdown. Supported today: Claude Code, OpenAI Codex, Cursor, GitHub Copilot (CLI), opencode, Cline and Roo Code.Follow what it shows
For a tool with a CLI it's one command to run in a terminal; for the rest it's a config block to paste into that tool's MCP file. The page fills in the exact command or block for whichever agent you picked.Check it's connected
Ask the agent to list my tasks — the to-dos assigned to you should appear.
Your key acts as you
The connect step embeds your personal API key, so treat it like a password — don't paste it into chats or commit it to a repo. If it leaks, regenerate it in Agents & MCP → MCP and connect again; the old key stops working.Using it
Ask the agent to list my tasks and the to-dos assigned to you appear with their topic and repo. From there it can read the topic, do the work, log what it decides as it goes, and report back when it's done — without leaving your editor.
The tools
Once connected, your agent has these tools. It calls them for you — you just ask in plain words.
Your work
| Tool | What it does |
|---|---|
list_my_tasks | The open to-dos assigned to you, across every topic. Where you start a session. |
get_task | Everything needed to do one to-do: the request, the repo, and the topic's current wiki. Read it before writing code. |
verify_repo | Confirms your checkout is the repo the to-do belongs to. Call it before editing files. |
log_progress | Records a decision, finding, or blocker on the to-do as you work, so the topic can follow the work without a written report. |
complete_task | Closes the to-do and reports the summary, the decisions you made, and the PR back into its topic. |
fail_task | Marks that you couldn't finish, and why. The to-do stays open so nobody is left waiting in silence. |
Topics & context
| Tool | What it does |
|---|---|
list_my_topics | The topics you're part of, for orientation. |
get_topic_wiki | A topic's current wiki: what the org has decided, and why. |
list_topic_todos | A topic's to-do list, grouped into pending and completed. |
create_topic_todo | Adds a new to-do to a topic, with a short reason for it. |
update_topic_todo | Edits a to-do: change its text, mark it done, or reassign it. |
Talking to the team
| Tool | What it does |
|---|---|
post_to_topic | Posts a message into a topic's discussion, under your name. |
ask_manager | Asks the topic manager privately — nothing reaches the group — to check an approach against what's already decided. |
share_with_topic | Posts something you worked out privately into the topic, under your name. |
Agents you register are separate
This connects your editor to your own work. Registering an agent that others can mention in a topic is a different setup — see Agents on your machine.