One platform to manage AI product development. Track delivery readiness, align code with business logic, and continuously assess quality and risk.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 16, 2026 · mcp.umaku.ai
44tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.umaku.ai/mcp
Skill page: https://www.mcpbundles.com/skills/umaku-mcp-11e3a1bf2b
Explore capabilities (44)
other 25
Showing 25 of 44
Showing 25 of 44 tools from the public preview. Connect the server to inspect the full live tool list.
Projects6
Kanban5
Sprints5
Bugs4
Comments3
Organizations2
Organizations List
other
organizations_list
List all organisations the authenticated user belongs to.
Returns each organisation's id and name.
Call this to resolve the organisation ID needed by `projects_list`.
Organizations List — List all organisations the authenticated user belongs to.
Returns each organisation's id and name.
Call this to resolve the organisation ID needed by `projects_list`.
Organizations Get — Get full details of a single organisation.
Projects My Access — List all projects the authenticated user can access across all organisations.
Call this first to discover available project IDs before using other tools.
Projects List — List projects in an organisation, with optional filters.
Projects Get — Get full project details: name, description, status, tech stack,
charter, milestones, and feedback history.
Note: member list is not included in this response. Use
`projects_get_members` to fetch the full member list with roles.
The feedback_history field contains agentic feedback reports. Each
report is one of four types:
- sprint_inclusion: sprint planning and task inclusion analysis
- bugs_finder: automated bug detection report
- code_quality: code quality assessment
- devops_compli
Projects Get Dashboard — Get project dashboard: sprint metrics, completion percentage, and timeline.
Projects Get Members — List all members of a project with their roles and user IDs.
This is the correct tool to use when you need to resolve a person's name
to a user ID — for assigning tasks or bugs, or for @mentions in comments.
It is scoped to the project and accessible to all project members.
Projects Get Descoped Tasks — Get the list of pending agentic descope requests for a project.
During a sprint, the agentic service analyses task progress and flags
incomplete tasks it believes should be descoped (e.g. not enough progress,
blocked, or unlikely to finish). Each flagged task becomes a descope
request that a PM must act on:
- Accept: moves the task to the 'Descoped' column in the BACKLOG sprint
- Reject: dismisses the request, task stays in its current sprint
This endpoint returns the tasks currently pend
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
One platform to manage AI product development. Track delivery readiness, align code with business logic, and continuously assess quality and risk.
How do I connect Umaku to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does Umaku provide?
Operate this server?
Request removal if you do not want Umaku listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Umaku?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in project management
Other MCP servers in this category from the directory index
Sprints List — List sprints for a project.
Each sprint includes name, goal, dates, status, and progress percentage.
Every project has a built-in sprint named 'BACKLOG' (status: 'planning').
It is a permanent container for unassigned or descoped tasks — it never
starts or completes. Exclude it when showing sprint progress to users.
Completed sprints include an agentic feedback field with up to four reports:
- sprint_inclusion: sprint planning and task inclusion analysis
- bugs_finder: automated bug detect
Sprints Get Active — Get the currently active sprint for a project.
Returns the sprint with its goal, dates, and progress.
Returns an empty list if no sprint is currently active.
Sprints Get — Get full sprint details: goal, dates, status, progress percentage,
total/completed task counts, and feedback for completed sprints.
Sprints Get Timeline — Get timeline visualization data for all sprints in a project.
Similar to Jira's timeline view. Returns all sprints (BACKLOG excluded)
with their tasks and calculated timeline boundaries:
- timeline_start: earliest task start_date in the sprint
- timeline_end: latest task end_date in the sprint
- tasks: minimal task data (name, start_date, end_date, column)
Useful for understanding the project schedule and identifying
sprints or tasks that have no dates set.
Sprints Move Tasks — Move one or more kanban tasks to a different sprint.
All tasks and the target sprint must belong to the same project.
Column assignment is automatic based on the move direction:
- Backlog → regular sprint: task column is set to 'TODO'
- Regular sprint → backlog: task column is set to 'In Planning'
- Regular sprint → regular sprint: task column is unchanged
The BACKLOG is a special built-in sprint that always exists for every
project. It holds unassigned or descoped tasks. To move tasks
Kanban Get Board — Get the full kanban board for a project: all columns and their tasks.
IMPORTANT: sprint_ids is required to see tasks. If omitted, the board
returns the column structure only — all task lists will be empty.
Use `sprints_get_active` first to get the active sprint ID, then pass
it here to see the current work.
Tasks in the BACKLOG sprint (the built-in unassigned/descoped container)
can be retrieved by passing the BACKLOG sprint ID. Get it from
`sprints_list` — it's the sprint named 'BACKLOG' with
Kanban Create Task — Create a new task in a kanban column.
The description field is rendered in a rich text editor — always write
it as HTML. For developer tasks use this structure:
<h3>User Story</h3>
<p>As a [role], I want [goal] so that [reason].</p>
<h3>Acceptance Criteria</h3>
<ul>
<li>criterion 1</li>
<li>criterion 2</li>
</ul>
Kanban Update Task — Update one or more fields of a kanban task. Only provided fields are changed.
The description field is rendered in a rich text editor — write it as HTML.
Kanban Move Task — Move a task to a different column and/or position.
Kanban Delete Task — Permanently delete a kanban task. This cannot be undone.
Bugs List — List bugs for a project.
Each bug includes title, severity, status, days_open, and comment count.
Bugs Get — Get full bug details: title, description, steps to reproduce,
severity, status, assignee, linked commits, and days open.
Bugs Create — Report a new bug on a project.
Bugs Update — Update one or more fields of a bug. Only provided fields are changed.
Comments List — List all comments on a kanban task, bug, or project.
Returns threaded comments with reporter info and reply counts.
Results are cursor-paginated, newest first (20 per page by default).
The response includes 'next' and 'previous' cursor URLs for navigation,
plus 'has_next' and 'has_previous' flags. Pass the 'cursor' value from
a 'next' link to fetch the next page.
Comments Create — Add a comment to a kanban task, bug, or project. Supports threaded replies.
When mentioning users, always use their numeric ID in the message text (e.g. '@123'),
not their username. This ensures the mention stays correct even if the user later
changes their username. Use projects_get_members to resolve a name to an ID before
composing the message. Every mentioned user must also appear in the mentioned_users
list so the backend can validate and display the current username.
Comments Update — Edit the text of an existing comment. Only the comment author can edit.
When mentioning users, always use their numeric ID in the message text (e.g. '@123'),
not their username. This ensures the mention stays correct even if the user later
changes their username. Use projects_get_members to resolve a name to an ID before
composing the message. Every mentioned user must also appear in the mentioned_users
list so the backend can validate and display the current username.
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 44 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Umaku require?
Umaku may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.