What it does
Adds IterDone as a connector in Claude (claude.ai and Claude Desktop) so Claude can read and update your spaces, lists, tasks, comments and docs in a conversation. You sign in and approve access once, no API key to copy.
Who needs it
Anyone who already uses Claude and wants to ask it about their work, or have it create and update tasks, without leaving the chat.
Why use it
Claude acts as you, with your role and your permissions, limited to the read or write scope you approve. Each connection shows up as its own entry under Admin > API Keys and can be revoked at any time.
How it works
Connecting takes about a minute. The server URL to enter is https://iterdone.com/mcp (no /task or workspace name in it).
- Add a custom connector. In Claude, open Customize > Connectors, click Add, then Add custom connector.
Customize > Connectors > Add > Add custom connector.
- Name it and paste the URL. Name:
IterDone. URL:https://iterdone.com/mcp. Click Continue.
Enter the name and the URL https://iterdone.com/mcp.
- Leave the OAuth defaults and click Add. "Register automatically" is detected; no client ID or headers are needed.
Keep "Register automatically" and click Add.
- Continue connecting. Claude sends you to IterDone. If it asks you to confirm, choose Continue connecting, and sign in to IterDone if you are not already.
Confirm that you started this connection from Claude.
- Allow access. The consent page names the workspace and the site you return to (claude.ai). Click Allow access. Claude shows the connector as Connected.
Approve the connection. Claude gets your permissions, never more.
Check it works. Start a new chat, enable the IterDone connector, and ask Claude to run whoami or list_spaces. Data coming back means the connection works. The connection also appears as a "Connector: ..." row under My API Keys.
Other AI agents. These steps apply to other AI tools too, such as Grok, ChatGPT, Gemini, Cursor or any assistant with MCP support: find its option for adding a custom or remote MCP connector (menu names differ), enter the same URL, https://iterdone.com/mcp, and approve access on the IterDone consent page. The screenshots above are from Claude. Clients that only accept a static key can use an API key instead.
Try it. Start a conversation, enable the IterDone connector, and ask for things like:
- "What tasks are assigned to me and due this week?"
- "Create a task called 'Review Q4 budget' in the Finance list, due Friday, and assign it to me."
- "Mark the 'Launch checklist' task as In Progress and add a comment that design sign-off is done."
- "Summarize what changed in the Website space and list anything blocked."
- "Log 45 minutes on the 'Vendor onboarding' task."
What Claude can do. The connector exposes the same operations as the REST API: spaces, folders and lists, tasks (create, update, move, assign, archive, delete), statuses, comments, tags, custom fields, checklists, dependencies, time tracking and timers, goals, views, docs, attachments, templates, webhooks, automations and invitations. Frequently used tools are named directly, for example whoami, list_spaces, list_tasks, get_task, search, create_task, set_task_status, add_comment, assign_user and add_time_entry. Everything else is reachable through list_operations and describe_operation, which list and describe the available operations, and invoke_read_operation and invoke_write_operation, which run them. Tools are marked read-only or destructive so Claude can ask before changing or deleting anything.
Access and revocation. Claude can only see and change what you can. Approving a connection mints one entry in Admin > API Keys; revoke it there and Claude loses access immediately. If your workspace restricts members from creating API keys, only an Owner or Admin can approve a connection. See the Privacy Policy for how connector data is handled.
Other clients. Claude Code, Claude Desktop with a config file, and any other MCP client can instead use an API key; see API Keys & Webhooks.