Your tracker, wired into your AI.
The dotby MCP connector lets Claude, Cursor, and any MCP-compatible assistant work your board directly — read tasks, create them, comment, assign, and ship — all through your own account.
$ claude mcp add --transport http dotby https://api.dotby.app/mcp$ claude mcp login dotby✓ Connected as you@team.com — 73 tools readyYour AI assistant and your tracker live in different windows.
You ask an assistant to plan the sprint, draft the tickets, summarize what is blocked — then you copy it all across by hand, one task at a time.
MCP closes that gap. Your assistant reads and writes your real board, in real time, with the exact permissions you already have.
Powerful, but never a back door.
Connect in two commands
Add the dotby server to your assistant and sign in once. No API keys to generate, store, or rotate — OAuth does the work.
Set it up in under a minute.
It can't do what you can't
Every tool call runs as you, through the same checks as the app. A guest stays a guest; a manager stays a manager. The connector adds no new access path.
Zero extra surface area to secure.
From board to backlog
Read and search tasks, create and move them, comment, assign, label, link, and manage projects — all from a chat prompt.
Your tracker, where your thinking already happens.
Three steps to a connected board.
Be on Pro
The connector is a Pro feature. Make sure your workspace is on Pro or Enterprise.
Copy your endpoint
In dotby, open Settings → Integrations and copy your workspace's MCP URL.
Add it to your assistant
Run the two commands, then authorize with your dotby account. You are connected.
What each role can do over MCP
The connector never grants more than the app does. These are the same roles that govern your workspace — admin, manager, member, and guest — applied to every tool call.
| Capability | Guest | Member | Manager | Admin |
|---|---|---|---|---|
| Connect & sign in (whoami) | ✓ | ✓ | ✓ | ✓ |
| Read projects, tasks & comments | ~ | ✓ | ✓ | ✓ |
| Search across the workspace | ~ | ✓ | ✓ | ✓ |
| Comment on tasks | ~ | ✓ | ✓ | ✓ |
| Edit tasks — assign, label, move, link | ~ | ✓ | ✓ | ✓ |
| Create & archive tasks | – | ✓ | ✓ | ✓ |
| Delete tasks permanently | – | – | ✓ | ✓ |
| Create, edit & archive projects | – | – | ✓ | ✓ |
| Workspace settings, members & billing | – | – | – | – |
- 1Guests only reach the specific projects they have been invited to, and can edit tasks only where they have been granted editor rights — everywhere else their access is read-only.
- 2Deleting a task requires project-admin rights, so in practice it is a manager or admin action.
- 3Workspace settings, billing, and member management are not exposed over MCP at all — those stay in the app UI.
- 4The connector is Pro-gated: the whole workspace must be on Pro or Enterprise before anyone can connect.
73 tools, grouped by intent
Every tool maps to an existing dotby action — nothing new to learn, nothing to trust blindly.
Read
- ✓whoami
- ✓list projects
- ✓list & search tasks
- ✓get task detail
- ✓my tasks
- ✓sub-tasks
- ✓comments & relations
- ✓states, labels & fields
- ✓initiatives & progress
- ✓pages & page tree
- ✓sprints
- ✓time entries & running timer
- ✓members
Write
- ✓create task
- ✓update task
- ✓move on board
- ✓set assignees
- ✓add / remove labels
- ✓custom fields
- ✓comment
- ✓link tasks
- ✓attach files
- ✓create & update initiatives
- ✓create & edit pages
- ✓create & update sprints
Manage
- ✓archive task
- ✓delete task
- ✓delete attachment
- ✓complete & archive sprints
- ✓archive pages & folders
- ✓create project
- ✓update project
- ✓archive project
Built to be safe by default.
- OAuth, not API keys. You authorize through Clerk with your own dotby login — there is no long-lived secret to leak or rotate.
- Rides your role. Each call passes the same workspace and per-project checks as the app, every time.
- Tenant-isolated. A resource in another workspace looks identical to one that does not exist — no cross-tenant probing.
- Pro-gated. Only Pro and Enterprise workspaces can open the connector in the first place.
Questions, answered.
What is MCP?+
The Model Context Protocol is an open standard that lets AI assistants securely call tools in the apps you use. dotby exposes your workspace as a set of MCP tools.
Which assistants work?+
Any MCP-compatible client — Claude desktop and Claude Code, Cursor, and a growing list of others. If it speaks MCP over HTTP, it connects.
Do I need to be an admin?+
No. Any member can connect using their own account, and the connector always acts with exactly your role — no more, no less.
Is my data safe?+
Yes. Authentication is OAuth through Clerk, every call is gated by your existing permissions, and nothing is exposed that you could not already do in the app.
What does it cost?+
The connector is part of Pro. Your workspace needs to be on Pro or Enterprise, and then any member can connect.
Let your assistant work the board.
Connect dotby to your AI in under a minute. Included with Pro.