Todo4you speaks the Model Context Protocol. Connect Claude, Cursor, or any MCP-aware assistant and let it create and update tickets, assign members, manage checklists, track time, and report on your projects - all through natural language.
One URL for every client. No local Node install, no self-hosting required.
Each token can be read-only or read/write, and limited to the projects you choose.
Claude Code, Claude Desktop, Cursor, Zed, or anything that speaks Streamable HTTP MCP.
Every action goes through the same REST API the web app uses - no stale state, no re-syncing.
Here are a few examples of what you can say to an assistant once MCP Access is connected.
Show me the open tickets in TDL and group them by priority.
Create a bug in TDL titled "CSV importer fails on quoted commas" with high priority.
Move TDL-47 to review and leave a comment linking to the pull request.
Summarise what my team shipped this week across all my projects.
Turn this email thread into a properly formatted ticket in the Support project.
Which tickets assigned to me are in review? Add a comment pinging Alice on each.
Open TDL-120, set priority to urgent, assign it to Bob, and start a timer for me.
Break this ticket into checklist items: design, implement, write tests, update changelog.
How much time did I log on TDL-47 this sprint, and which entries were longer than an hour?
In Profile - MCP Access, name your token, pick read-only or read/write, and select which projects it may access.
Paste the server URL and your token into Claude Code, Claude Desktop, Cursor, or any other MCP client.
Ask your AI assistant to list projects, create tickets, or move work forward. Revoke the token any time from the same screen.
{
"mcpServers": {
"todo4you": {
"type": "http",
"url": "https://mcp.todo4you.com/mcp",
"headers": {
"Authorization": "Bearer t4y_mcp_your_token_here"
}
}
}
}
The MCP server exposes a focused set of well-defined tools, each mapped to a REST API call. Read tools work with any token; write tools require read/write scope.
| Tool | Scope | Description |
|---|---|---|
| Projects | ||
list_projects |
read | List the projects the token is scoped to. |
project_stats |
read | Open-ticket counts per status for a project. |
project_statuses |
read | Status slugs and categories configured on the project. |
list_project_members |
read | List members of a project with their user IDs and roles. |
list_tags |
read | List the tags defined in a project. |
| Tickets | ||
list_tickets |
read | List non-archived tickets, optionally filtered by status. |
search_tickets |
read | Full-text search tickets in a project by title or description. |
get_ticket |
read | Full ticket detail: description, comments, checklist, tags, assignees, blockers, attachments, and time summary. |
create_ticket |
write | Create a ticket with title, type, priority, and description. |
update_ticket |
write | Update title, description, type, priority, deadline, estimation, or tags. |
move_ticket |
write | Move a ticket to a different status slug. |
archive_ticket |
write | Archive a ticket, hiding it from the board. |
delete_ticket |
write | Permanently delete a ticket. Creator or project manager only. |
assign_member |
write | Assign a project member to a ticket. |
unassign_member |
write | Remove an assignee from a ticket. |
| Comments | ||
list_comments |
read | List the comment thread on a ticket. |
add_comment |
write | Add a Markdown comment to a ticket. |
update_comment |
write | Edit an existing comment. Authors only. |
delete_comment |
write | Delete a comment. Author or project manager only. |
| Checklist and blockers | ||
add_checklist_item |
write | Add a checklist (subtask) item to a ticket. |
toggle_checklist_item |
write | Toggle a checklist item between open and done. |
update_checklist_item |
write | Update the text of a checklist item. |
delete_checklist_item |
write | Delete a checklist item. |
add_blocker |
write | Mark another ticket as a blocker of this ticket. |
remove_blocker |
write | Remove a blocker relationship. |
| Tags | ||
create_tag |
write | Create a new tag in a project. |
update_tag |
write | Update a tag's name or color. |
delete_tag |
write | Delete a tag from a project. |
| Time tracking | ||
list_time_entries |
read | List all time entries on a ticket with a total in minutes. |
running_timer |
read | Get the current user's running or paused timer, if any. |
start_timer |
write | Start a live timer on a ticket. |
stop_timer |
write | Stop a running or paused timer and record the elapsed minutes. |
pause_timer |
write | Pause a running timer, preserving accumulated minutes. |
resume_timer |
write | Resume a paused timer. |
add_time_entry |
write | Log a manual time entry on a ticket. |
update_time_entry |
write | Update the minutes on a time entry. |
delete_time_entry |
write | Delete a time entry. |
Tokens are shown once and stored SHA256-hashed. We cannot recover them if lost.
A token cannot change account settings, membership, billing, passkeys, or 2FA, even on read/write scope.
Delete the token in your profile - the next request fails. No caching, no delay.
MCP Access is free. Create a token and connect your favourite MCP client in minutes.
Get started free