AI tools (MCP)

An AI tool - Claude, ChatGPT, an IDE - can reach your workspaces through Plan Things Better's MCP server, with an API key. It sees what you see and acts as you. Connect an AI assistant (MCP) takes you to your keys - it's on the search screen (with no tab open), and ⌘K / CtrlK finds it when you type "mcp", "ai", "claude" or "api key". If it isn't there, connecting AI tools isn't available right now.

#Connecting a tool

1. In Settings → Account → API keys, press + (Make an API key) and give the key a name - the tool's name, say "Claude" - then press Make key.
2. Copy the key from its row (Show displays it in full), and the Server address (MCP) above the list. When the REST API is available too, it's under the AI client (MCP) tab.
3. In your AI tool, add a connector with that address, sending the key as Authorization: Bearer <key>.

If the tool says the server needs an API key, it isn't sending one. If it says the key isn't valid, the key is mistyped or was revoked - copy it again, or make a new one.

The connector finds things the way search does, in the same query language across kinds: ask it for kind:project status:todo or project.name:website and it gets just those.

It reads views and dashboards the way the hubs show them: which Space each is kept in (one in a Space counts only that Space's tasks), when anyone last opened it, and which ones nobody has opened in 60 days. A project, milestone, label or person comes with the views and dashboards that show it, so it can tell what a rename or a delete would change.

#What it can do

A new key can only read: your tasks, projects, milestones, views, dashboards, docs and tables, Spaces, chat, Activity, your Inbox, your favorites and the Trash. Two switches on its row let it do more - always as you, and only where your role allows:

• Let it make changes - create and update tasks (and link them, or move them to another Space), change many tasks the same way in one go (it shows what it would change first, and does nothing until it's confirmed; 200 tasks at most), make and change projects, milestones, saved views, dashboards (and their charts), labels, custom fields, templates and docs (filing them in hub folders, and making, renaming and moving the folders - or moving everything in one to another Space, as one move), move several projects to a Space together (showing what would move first), make Spaces and chat channels (it can't add people to a Space - that stays in the app), write tables' rows, comment and post in chat, edit or delete your own comments and messages, put a task's changes back from Activity, mark your Inbox read, add to and remove from your favorites (add_favorite, remove_favorite), change your theme and accent (update_appearance), make and change brands and set a project's or Space's brand (create_brand, update_brand; logos are uploaded in the app), and change the workspace's statuses, priorities and types. Besides table rows and your own comments and messages, the only things it can delete are statuses, priorities and types, as Settings does. Comments and messages it deletes are gone for good, as in the app.
• Let it move things to the Trash - move tasks, docs, a task's checklists, projects, milestones, saved views, dashboards and custom fields to the Trash (move_to_trash) and bring them back (restore_from_trash), the same as Delete and Restore in the app, one item at a time by its key. It's a switch of its own, off on every new key, and Let it make changes never turns it on - leave it off unless you want the tool to clean up. It never deletes anything for good: the Trash keeps what it moves for the workspace's usual time, and you can restore it from there.

Seeing what's in the Trash (list_trash) needs neither switch: it only reads, like the Trash page, so every key can. When a release adds a tool, a key with the matching switch on gets it too, and your Inbox says what the key can now do.

Changes a key makes show up in your open window as they happen, even when you're the only person in the workspace: while a key that can change things has been used in the last 30 minutes, the app listens for live updates, and it lets go again once the key goes quiet.

#Trying it in the demo

The demo (Try the demo on the home page) can be connected to an AI tool too. Its account comes with a key named "Claude" that may make changes, and the demo's Activity, comments and #launch chat show what was done through it - "You via Claude", and a teammate's too. Copy that key with Show, or make one of your own, and connect your tool as above. It works on the demo, as the demo's account, with the same switches and rules as any key.

A demo account's keys have limits: at most 5 at once, and 60 requests a minute (600 an hour), so a tool working fast may be asked to wait a moment. They're deleted with the demo - sign up to keep a connection.

For AI tools, the site describes its MCP server - the address, the switches and every tool - at /llms.txt.

To use your workspaces from your own code instead, see The REST API.