GitScrum Tasks MCP. Manage tasks and track progress without leaving your chat.

Listen up. GitScrum Tasks isn't just another API endpoint you gotta juggle; it’s your whole task management system talking directly through your AI client. You manage the entire lifecycle of a ticket—from idea to done—without ever leaving your chat window or IDE. Forget context-switching between Jira and Slack; you handle everything right here.

Finding What You Need

You don't have time clicking through endless Kanban boards. If you gotta find something, this thing handles it fast. You can pull up all the details for a specific ticket using its unique ID with get_task, or if your team uses human-readable codes—like 'WEB-42'—you just use get_task_by_code. Need to see what's happening across the board? Use list_tasks; you can filter results instantly by status, assignee, date range, and more.

For a personal view, you've got my_tasks to pull up everything assigned directly to you, or if you just wanna know what’s due today, my_today_tasks shows it right up.

It also keeps tabs on dependencies. If you open a ticket, the system finds all related tickets using related_tasks. You can check out every subtask linked to a main task with list_subtasks, and if you need to see what other checklist items are attached, use list_checklists.

Moving Tickets Through Workflow

When it comes time to move things along, you've got plenty of options. You change the overall status of a task—marking it complete or reopening it—using toggle_task_done. If someone else owns the ticket, you can assign ownership with assign_member or free them up using unassign_member. Need to shift a project entirely? Use move_task_to_project to transfer an existing task ticket between different projects.

You can also make sure tickets are structured right by connecting one ticket to another as a sub-step via link_subtask, or break that connection using unlink_subtask. To start fresh work, you've got duplicate_task, which makes an exact copy of any existing ticket.

Building Out the Details and Talking Shop

You need to add depth? You can apply story points or effort estimates with set_task_estimate so the team knows how big this thing is. For detailed tracking, you build out checklists using create_checklist_item, and if something gets checked off, you toggle it done or undone with toggle_checklist_item. All communication stays right on the ticket.

You can write a brand new comment using create_comment—and yeah, you get rich text formatting for detailed notes. If you mess up your thoughts, don't sweat it; use update_comment to edit an existing note without deleting the history. You can even wipe out old comments entirely with delete_comment.

Structuring and Maintaining Projects

This server lets you build the project structure itself. If the team needs a new task category, you define it using create_task_type, which also assigns custom colors to those types. You can create a brand-new ticket from scratch with create_task, or if that’s not enough, you can modify general details on any task—changing the title or description while keeping its ID intact—with update_task.

If a ticket needs more help tracking progress, you can link existing tickets to it as subtasks using link_subtask. You're always in control: if you need a complete history of notes, use list_comments and list_subtasks; if you gotta see what effort levels the team uses, pull that list with list_effort_levels.

Finally, it helps you manage your workload by listing all tasks assigned to you (my_tasks) or pulling up only those due today using my_today_tasks. You can also check out every custom task type defined in the project with list_task_types, which shows you their hex colors for visual reference. If a ticket has checklist details, you pull them all with list_checklists.