Tidy up your workspace
The connection point between Codex or Claude Code and Tooon. Take stock of projects, tasks and pages, map how they connect, and decide together how to organize them. Once you've checked a proposed change, apply it right there.
On Solo and up, connect with a workspace API key.
From reading to applying changes, through one connection.
Agents can't see tools the key doesn't have access to.
- Get the big picture
tooon_capabilities checks first what it can do and what it can't fetch.
- Business lists
Fetches projects, tasks, clients, partners and more, all the way to the end.
- Pages and databases
Reads page content, reference blocks, and database fields and rows.
- Follow the links
Fills in connections from where things are shown, projects, backlinks and attachments.
- Units
Checks the sidebar units and the projects shown in each.
- Propose and applyWrite access
tooon_preview_change drafts a change; only the ones you've checked are applied with tooon_apply_change.
First, read
Connect with a read-only key and the agent goes through every project, task, client and page. Lists it couldn't fetch and areas without access are kept apart from lists that are simply empty.
Same name, or same thing?
IDs and references come through as they are, so the agent can draw parent, reference and where-shown as separate lines. A page shown in two units isn't counted as a duplicate.
See the proposed change,
The agent always drafts a proposed change first. Check what it touches and the before and after, and when you apply it, Tooon checks access and edits again before saving. A proposal is valid for 5 minutes. If someone else updated it first, the agent drafts again from the new state.
Write accessWhat people decide
Through MCP you can only create and update projects, tasks and clients. Deleting, moving or merging pages, invoicing and payments, publishing and sending anything outside aren't possible. It can suggest what to merge, but never merges on its own.
Codex
There's one endpoint per workspace. Config examples for Codex and Claude Code are in the setup guide. Pass the key as an environment variable where the agent runs, never in a config file or a chat.
Connected in three steps.
- 1Move to Solo or up
MCP works in Solo, Pro and Business workspaces.
- 2Create a key for the job
An admin creates it in Settings → Integrations. For taking stock, pick read access only.
- 3Set up your agent
Swap in your workspace ID in the guide’s config example and pass the key as an environment variable.
Before you connect, start here.
Clean up a messy workspace, with an agent.
On Solo and up, create an API key and connect right away.