For AI agents: a documentation index is available at /llms.txt. A markdown version of this page is available at /guide/mcp/tools.md.
MCP/AI Connect
Tools
All 212 MCP tools, grouped by domain, with the OAuth scope each one needs.
The server advertises 212 tools across 15 domains. Each one asserts a scope before it runs, so what your assistant can actually do is decided at consent time, not by this list.
Ask the server, not this page
Tool names are part of the server's contract and can change between
deployments. The authoritative list for the endpoint you are pointed at always
comes from a tools/list call, or just ask your assistant: "what Orangescrum
tools do you have?"
#Coverage
| Domain | Tools | Read scope | Write scope |
|---|---|---|---|
| Projects | 5 | mcp:projects.read | mcp:projects.write |
| Tasks | 8 | mcp:tasks.read | mcp:tasks.write |
| Task comments | 4 | mcp:tasks.read | mcp:tasks.write |
| Dependencies, links and labels | 9 | mcp:tasks.read | mcp:tasks.write |
| Attachments | 1 | mcp:tasks.read | n/a |
| Backlog hierarchy | 5 | mcp:epics.read | mcp:epics.write |
| Sprints | 7 | mcp:sprints.read | mcp:sprints.write |
| Timelogs | 3 | mcp:timelogs.read | mcp:timelogs.write |
| Users | 3 | mcp:users.read | n/a |
| Project context ("memory") | 2 | mcp:context.read | mcp:context.write |
| Document search | 1 | mcp:documents.read | n/a |
| Test Lab | 69 | mcp:tests.read | mcp:tests.write |
| Versions and releases | 29 | mcp:releases.read | mcp:releases.write |
| Scaled Agile (SAFe) | 46 | mcp:safe.read | mcp:safe.write |
| Checklists | 20 | mcp:checklists.read | mcp:checklists.write |
Access is the scope family a tool asserts. Tools marked destructive delete or irreversibly change data; clients that honor MCP tool annotations can ask you before running them.
#Projects
Read, create, update and search the projects in a workspace.
| Tool | Access | What it does |
|---|---|---|
list_projects | read | List all projects accessible to the partner with optional filtering and pagination |
get_project | read | Get detailed information about a specific project. |
create_project | write | Create a new project with specified details including name, description, and dates |
update_project | write | Update an existing project. |
search_projects | read | Search projects by free-text query and optional filters. |
#Tasks
List, read, create and update tasks, and look up the statuses and types a project accepts.
| Tool | Access | What it does |
|---|---|---|
list_tasks | read | List tasks with optional filtering by project ID, user ID, status, and pagination |
get_task | read | Get detailed information about a specific task: its fields, its dependencies (predecessors), its dependents (successors), its linked tasks, and counts plus a preview of its comments and attachments. |
create_task | write | Create a new task in a project with specified details including title, description, priority, and assignment |
update_task | write | Update an existing task. |
search_tasks | read | Search tasks by free-text query and optional filters (project, status, priority, assignee). |
list_task_statuses | read | List the workflow statuses configured for a project, in workflow order. |
list_task_types | read | List the task types available in the workspace (e.g. |
list_tasks_v2 | read | List tasks with strict project filtering, mine/status filters, deterministic pagination, and normalized identifiers |
#Task comments
Read and post comments on a task. Posting does not send the notifications the web app would.
| Tool | Access | What it does |
|---|---|---|
list_task_comments | read | List the comments on a task, newest first, paginated. |
get_task_comment | read | Get a single comment on a task, with its body unclipped. |
add_task_comment | write | Post a comment on a task as the authenticated user. |
update_task_comment | write | Edit a comment on a task, replacing its body. |
#Dependencies, links and labels
Scheduling dependencies between tasks, plain links, and labels.
| Tool | Access | What it does |
|---|---|---|
list_task_dependencies | read | List a task's dependencies (the tasks it waits on) and its dependents (the tasks waiting on it), each with the dependency type: finish-to-start, start-to-start, finish-to-finish or start-to-finish. |
add_task_dependency | write | Make a task depend on another task (blocked-by): the task named in task_id waits on the task named in depends_on_task_id. |
update_task_dependency | write | Change the type of an existing dependency between two tasks: finish-to-start, start-to-start, finish-to-finish or start-to-finish (FS/SS/FF/SF also accepted). |
list_task_links | read | List the tasks linked to a task (relations such as related-to or duplicated-by), each with the link id needed to change it, plus the relation types this workspace has available. |
add_task_link | write | Link one task to another (a "related to" / "duplicated by" style relation, with no scheduling meaning — use add_task_dependency for that). |
list_task_labels | read | List the labels on a task and the active labels available to its project (project labels plus company-wide ones). |
add_task_labels | write | Add labels to a task. |
remove_task_label | write, destructive | Remove one label from a task, by label id or name. |
update_task_link | write | Change the relation of an existing link between two tasks — e.g. from related-to to duplicated-by. |
#Attachments
Files attached anywhere in a task's comment thread.
| Tool | Access | What it does |
|---|---|---|
list_task_attachments | read | List the files attached to a task, newest first, paginated. |
#Backlog hierarchy
Epics, features, stories and subtasks. Orangescrum v4 projects only.
| Tool | Access | What it does |
|---|---|---|
get_epic | read | Get an Epic and the full hierarchy beneath it: its Features, the Stories under each Feature, and the tasks (and their subtasks) under each Story. |
create_epic | write | Create an Epic, the top-level Scrum backlog item, in a project. |
create_feature | write | Create a Feature under an existing Epic. |
create_story | write | Create a Story in a project. |
create_subtask | write | Create a child work-item under a Story or a Task. |
#Sprints
Create, start and complete sprints, and move work in and out of them.
| Tool | Access | What it does |
|---|---|---|
list_sprints | read | List sprints for a project. |
get_sprint | read | Get a single sprint by its numeric id or uniq_id. |
create_sprint | write | Create a new sprint (also called a milestone, iteration or release) with a name in a project. |
update_sprint | write | Update a sprint's title, description, or planned dates. |
start_sprint | write | Start a sprint. |
complete_sprint | write | Complete (close) a sprint. |
assign_task_to_sprint | write | Move a task into a sprint, or back to the backlog. |
#Timelogs
Log time against tasks and read it back.
| Tool | Access | What it does |
|---|---|---|
list_timelogs | read | List timelogs for the authenticated partner user, with optional filters by project, task, and date range |
create_timelog | write | Log time against a task. |
update_timelog | write | Update a timelog entry. |
#Users
The connected user and the workspace directory.
| Tool | Access | What it does |
|---|---|---|
get_current_user | read | Return authenticated user profile including timezone, roles, and default workspace/company |
list_users | read | List users in the company with optional free-text search on name/email and pagination |
get_user | read | Get detailed information about a specific user. |
#Project context ("memory")
Standing instructions the assistant reads at the start of a conversation.
| Tool | Access | What it does |
|---|---|---|
get_project_context | read | Retrieve the standing context ("memory") saved for this workspace — background, conventions, and instructions to keep in mind. |
add_project_context | write | Save a standing context ("memory") entry so it is recalled in future conversations. |
#Document search
Semantic search over documents uploaded to the workspace.
| Tool | Access | What it does |
|---|---|---|
search_documents | read | Search documents uploaded to this OrangeScrum workspace (PDFs, Word, Excel, images) by meaning and return the most relevant excerpts with their source document. |
#Test Lab
Test cases, suites, plans, runs, scenarios, strategies, baselines and defects from Test Lab.
#Repository
| Tool | Access | What it does |
|---|---|---|
list_test_lookups | read | List the allowed values for Test Lab fields in this workspace: test case priority, type, state, template and automation status, and defect severity, priority, status, resolution and root cause. |
create_test_case | write | Create a test case in the Test Lab repository (/test-lab#/repository) of a project. |
list_test_cases | read | List Test Lab test cases (the /test-lab#/repository list), ordered by project and TC number. |
get_test_case | read | Get a Test Lab test case with all its fields and steps, plus its links (tasks, cases, defects, runs), comments, attachments and latest run results. |
update_test_case | write | Update a Test Lab test case. |
delete_test_case | write, destructive | Delete a Test Lab test case. |
list_test_case_versions | read | Version history of a Test Lab test case, newest first (up to 30). |
list_test_suites | read | List the Test Lab suites (the folder tree of the repository) of a project, with parent ids and case counts. |
create_test_suite | write | Create a test suite (a folder in the Test Lab repository, /test-lab#/repository) in a project, optionally inside a parent suite. |
update_test_suite | write | Rename a Test Lab suite, change its description, or move it under another suite of the same project. |
list_test_datasets | read | List the parameter datasets a project can use (its own plus workspace-wide). |
add_test_case_tags | write | Add tags to one or more Test Lab test cases (like the Add tag bulk action). |
export_test_cases | read | Export Test Lab test cases as CSV, the same format as the Test Lab Export button (TC id, title, priority, steps as "step => expected | ...", suite, owner, ...). |
create_test_dataset | write | Create a Test Lab parameter dataset: named columns and rows of values. |
update_test_dataset | write | Update a Test Lab dataset: rename, change description or project, or replace its columns and rows. |
list_test_shared_steps | read | List Test Lab shared steps: reusable step blocks a project's cases can copy in. |
update_test_shared_step | write | Edit a Test Lab shared step block: rename it or replace its steps. |
list_test_custom_fields | read | List the Test Lab custom field definitions (workspace-wide) for test cases and / or defects, with their keys, types and options. |
create_test_custom_field | write | Create a Test Lab custom field for test cases or defects (workspace-wide). |
update_test_custom_field | write | Edit a Test Lab custom field: label, type, options, required, visible or order. |
#Comments, links and attachments
| Tool | Access | What it does |
|---|---|---|
list_test_comments | read | List comments on a Test Lab test case, defect or run (oldest first). |
add_test_comment | write | Add a comment to a Test Lab test case, defect or run (max 8000 chars). |
add_test_link | write | Link a Test Lab test case or defect to an OrangeScrum task, another test case, a defect or a run. |
remove_test_link | write, destructive | Remove a Test Lab link by its link id (shown in get_test_case / get_defect links). |
list_test_attachments | read | List the files attached to a Test Lab test case, defect, scenario or run result, newest first, each with a link that opens it in Orangescrum (images inline, other files download; the viewer must be signed in). |
#Scenarios and strategies
| Tool | Access | What it does |
|---|---|---|
list_test_scenarios | read | List Test Lab scenario records (the /test-lab#/scenarios screen) with their child counts. |
get_test_scenario | read | Get a Test Lab test scenario with its cases. |
create_test_scenario | write | Create a Test Lab test scenario in a project; it gets the next number in the project. |
update_test_scenario | write | Update a Test Lab test scenario; only the fields you pass change. |
delete_test_scenario | write, destructive | Delete a Test Lab test scenario (soft delete). |
set_scenario_cases | write | Attach test cases to a Test Lab test scenario (attach=true, default) or detach them (attach=false). |
list_test_strategies | read | List Test Lab strategy records (the /test-lab#/strategies screen) with their child counts. |
get_test_strategy | read | Get a Test Lab test strategy with its scenarios. |
create_test_strategy | write | Create a Test Lab test strategy in a project; it gets the next number in the project. |
update_test_strategy | write | Update a Test Lab test strategy; only the fields you pass change. |
delete_test_strategy | write, destructive | Delete a Test Lab test strategy (soft delete). |
set_strategy_scenarios | write | Attach test scenarios to a Test Lab test strategy (attach=true, default) or detach them (attach=false). |
#Plans and runs
| Tool | Access | What it does |
|---|---|---|
get_test_run_setup | read | List what a project's Test Lab runs and plans can use: configurations, environments and open sprints / milestones. |
list_test_plans | read | List Test Lab test plans (the /test-lab#/plans screen) with their case selection, configurations and run count. |
get_test_plan | read | Get a Test Lab test plan with the runs it has launched and their progress. |
create_test_plan | write | Create a Test Lab test plan: which cases to run (selection), against which configurations, for which sprint. |
update_test_plan | write | Update a Test Lab test plan; only the fields you pass change. |
launch_test_plan | write | Launch a Test Lab test plan: creates one active run per configuration (or one run without), each with an item per selected case (per dataset row for parameterised cases). |
delete_test_plan | write, destructive | Delete a Test Lab test plan (soft delete). |
list_test_runs | read | List Test Lab runs (the /test-lab#/runs screen) with progress stats. source=exploratory lists exploratory sessions. |
get_test_run | read | Get a Test Lab run with every item (case, steps with dataset values filled in, status, assignee, comment), its stats and the defects raised in it. |
create_test_run | write | Start a Test Lab run in a project. |
update_test_run | write | Rename a Test Lab run or change its description, environment, sprint or assignee. |
record_test_result | write | Record a result in an active Test Lab run: one item (with optional per-step results) or the same result on several items of one run. |
list_test_result_history | read | Result history of one Test Lab run item, newest first, with step results and any defect raised. |
close_test_run | write | Close (complete) a Test Lab run or end an exploratory session. |
rerun_failed_tests | write | Start a new Test Lab run containing the failed and blocked items of an earlier run. |
delete_test_run | write, destructive | Delete a Test Lab run (soft delete). |
#Exploratory sessions
| Tool | Access | What it does |
|---|---|---|
start_exploratory_session | write | Start a Test Lab exploratory session (the /test-lab#/explore screen): a run with a charter and no scripted items. |
add_exploratory_note | write | Log a finding in an active Test Lab exploratory session: a note, bug, idea or question. |
list_exploratory_notes | read | List the findings (notes, bugs, ideas, questions) of a Test Lab exploratory session. |
#Baselines
| Tool | Access | What it does |
|---|---|---|
list_test_baselines | read | List Test Lab baselines (frozen snapshots of a project's test cases, the /test-lab#/baselines screen). |
create_test_baseline | write | Freeze the active test cases of a project (or of a suite and its sub-suites) as a Test Lab baseline, to compare against or restore from later. |
compare_test_baseline | read | Compare a Test Lab baseline with the current test cases (default) or another baseline of the same project: which cases changed (and which fields), were added, removed or moved. |
restore_test_baseline | write | Restore test cases to their content in a Test Lab baseline. |
delete_test_baseline | write, destructive | Delete a Test Lab baseline and its frozen cases (permanent, as in Test Lab). |
#Defects
| Tool | Access | What it does |
|---|---|---|
list_defects | read | List Test Lab defects (the /test-lab#/defects list), newest BUG number first. |
get_defect | read | Get a Test Lab defect with all its fields, related defects, watchers, change history, links (tasks, cases, runs), comments and attachments. |
create_defect | write | Report a defect in Test Lab (/test-lab#/defects) for a project. |
update_defect | write | Update a Test Lab defect. |
set_defect_status | write | Move a Test Lab defect to another workflow status (default new, open, in_progress, fixed, retest, verified, closed, rejected, duplicate). |
delete_defect | write, destructive | Delete a Test Lab defect (soft delete, as in the Test Lab UI). |
add_defect_relation | write | Relate two Test Lab defects: duplicate_of, relates, blocks or blocked_by. |
remove_defect_relation | write, destructive | Remove a relation between two Test Lab defects by its relation id (from get_defect relations). |
#Versions and releases
Versions, releases, their items and progress, readiness, approval chains and release notes.
| Tool | Access | What it does |
|---|---|---|
list_versions | read | List versions (planned product versions such as 4.2) in one project, or across every project you can access when project_id is omitted. |
get_version | read | Get one version with its owner, dates, status, the statuses it can move to next, item and release counts, and its recent change history. |
create_version | write | Create a version in a project. |
update_version | write | Update a version's name, description, goal, owner or planned dates. |
transition_version | write | Move a version to another status: Draft, Planned, Active, On Hold, Released or Archived. |
delete_version | write, destructive | Delete a version (soft delete, as the Delete button in the app; the plugin calls this archiving). |
list_version_items | read | List the work items (epics, features, stories, tasks, defects) linked to a version, newest first, with title, number, status, due date and assignee. |
add_version_items | write | Link work items to a version in one all-or-nothing call (up to 100). |
remove_version_item | write, destructive | Unlink one work item from a version. item_id is the link id shown by list_version_items, not the task id. |
get_version_progress | read | Completion of a version: linked items done out of total, overall percent, and per type. |
get_release_roadmap | read | Roadmap of a project: its versions in planned start order, each with its releases. |
list_releases | read | List releases (shippable builds of a version, such as 4.2.1) for a version, a project, or every project you can access. |
get_release | read | Get one release with its version, type, dates, owner, status, approval chain status, the statuses it can move to next, item count and recent change history. |
create_release | write | Create a release under a version; it starts in Draft. release_number must be unique in the version (letters, digits, dot, dash, underscore, space; max 50). type is one of Major, Minor, Patch, Hotfix, Beta or Release Candidate. |
update_release | write | Update a release's name, description, type, planned date or owner. |
transition_release | write | Move a release to another status: Draft, Planned, Testing, Ready, Approved, Released, Rolled Back or Cancelled. |
delete_release | write, destructive | Delete a release (soft delete, as in the app). |
list_release_items | read | List the work items included in a release, newest first, with title, status and assignee. |
add_release_items | write | Include version items in a release, all or nothing (up to 100). |
remove_release_item | write, destructive | Remove one item from a release. item_id is the link id from list_release_items. |
get_release_readiness | read | Whether a release is ready to move to Ready: percent of its items done against the threshold for its type (Major and Minor 100, others 90), open stories, tasks and defects, and unresolved dependencies. ready is false when it has no items. |
list_my_pending_approvals | read | List release approval steps waiting for you, with the release, the level, and can_act (true when every lower level is already approved). |
get_release_approval_chain | read | The approval chain of a release: each level's approver, status, comment and time, the chain status (in_approval, approved, rejected, cancelled), and whether you can act now. |
approve_release_step | write | Approve a release approval step assigned to you. |
reject_release_step | write | Reject a release approval step assigned to you, with a required comment explaining why. |
cancel_release_approval_chain | write, destructive | Cancel the whole approval chain of a release (every live step). |
get_release_notes | read | Get a release's notes (markdown), whether they were generated or written by hand (is_manual_override), and when. |
generate_release_notes | write | Generate a release's notes from its items: New Features (epics, features), Improvements (stories, tasks) and Fixed Issues (defects). |
update_release_notes | write | Replace a release's notes with your own markdown. |
#Scaled Agile (SAFe)
Release trains, program increments, the program board, PI objectives, ROAM risks, WSJF, Inspect & Adapt and flow metrics.
#Agile Release Trains
| Tool | Access | What it does |
|---|---|---|
list_arts | read | List the workspace's Agile Release Trains (ARTs), newest first, with each train's cadence (PI and iteration length in weeks, whether it has an IP iteration), status, active team count and program increments. |
get_art | read | Get one Agile Release Train: its cadence and status, the teams on it (team_id and name), the teams that could still be attached (attachable_teams), the SAFe role holders (RTE, product manager, system architect, business owners, each with an assignment id), linked projects and its program increments. |
get_art_health | read | Health of an Agile Release Train at a glance: its current program increment and how far through it is (the Executing PI, else the one whose dates include today, else the newest), PI counts by status, the current PI's objectives and business value delivered (actual over planned), open ROAM risks, completion of work items planned onto the ART, dependency count and the Release Train Engineer. |
list_art_dependencies | read | List the backlog dependencies (blocks, related, duplicates, parent_of) that touch any work item planned onto an Agile Release Train, newest first — including dependencies on items in other trains, which is where cross-ART risk shows. |
create_art | write | Create an Agile Release Train. code is upper-cased and must be unique in the workspace. |
update_art | write | Update an Agile Release Train's name, code, description, program or cadence. |
archive_art | write | Archive an Agile Release Train (action archive) or bring an archived one back (action restore). |
attach_art_team | write | Attach a team to an Agile Release Train from today. get_art lists the teams that can be attached (attachable_teams). |
detach_art_team | write, destructive | Detach a team from an Agile Release Train as of today. |
attach_art_project | write | Link a project to an Agile Release Train, so its epics, features and stories appear in the train's backlog. |
detach_art_project | write, destructive | Unlink a project from an Agile Release Train. |
assign_art_role | write | Give a workspace member a SAFe role on an Agile Release Train: rte (Release Train Engineer), product_manager, system_architect or business_owner. |
revoke_art_role | write, destructive | Revoke a SAFe role assignment on an Agile Release Train as of today. |
#Program increments and the program board
| Tool | Access | What it does |
|---|---|---|
list_program_increments | read | List program increments (PIs), latest start first, with their iterations. |
get_program_increment | read | Get one program increment: its ART, theme, business context, dates, status (planning, executing, closed), iterations, PI objectives and ROAM risks. |
create_program_increment | write | Create a program increment (PI) on an ART, in Planning. |
update_program_increment | write | Update a program increment's name, theme, business context or dates. |
transition_program_increment | write | Move a program increment along its lifecycle: lock (Planning to Executing, which freezes its plan) or close (Executing to Closed). |
get_iteration | read | Get one iteration of a program increment: its dates, whether it is the IP iteration, the backlog items planned into it (planned_items) and the items placed in its program board cells (board_items). |
get_program_board | read | Get the program board of a program increment: its iterations (columns), the ART's teams (rows), the work items placed in each team-and-iteration cell with their committed load, and the dependencies touching those items, including ones reaching outside the PI. |
place_on_program_board | write | Place a work item (usually a feature) in a team-and-iteration cell of a program increment's board, with how much of the team's capacity it commits (1 to 100 percent, default 100). |
remove_from_program_board | write, destructive | Remove a placement from a program increment's board. |
#PI objectives, risks and confidence votes
| Tool | Access | What it does |
|---|---|---|
list_pi_objectives | read | List a program increment's team PI objectives, committed first, with planned business value (1 to 10) and, once recorded, actual business value. |
create_pi_objective | write | Add a PI objective: what a team (or the whole ART when team_id is omitted) intends to achieve, committed or as a stretch (uncommitted) objective, with planned business value 1 to 10 (default 5). |
update_pi_objective | write | Update a PI objective's description, team, committed flag or planned business value, or record the actual business value delivered (0 to 10), which business owners score at the end of the PI and which drives PI predictability. |
list_roam_risks | read | List a program increment's ROAM risks, newest first, each Resolved, Owned, Accepted or Mitigated, with its owner. |
create_roam_risk | write | Raise a risk on a program increment and ROAM it: resolved, owned (default), accepted or mitigated, optionally with an owner. |
update_roam_risk | write | Update a ROAM risk's description, owner or status (resolved, owned, accepted, mitigated). |
cast_confidence_vote | write | Cast your fist-of-five confidence vote (1 to 5) on a program increment's plan, for a voting round (default 1). |
get_confidence_vote_summary | read | Confidence vote results for a program increment, per round: number of votes and average overall and per team. |
#Backlog, dependencies and WSJF
| Tool | Access | What it does |
|---|---|---|
list_safe_backlog | read | List the SAFe backlog: epics, features and stories with their ART, PI, iteration, team, kanban state, rank and latest WSJF score. |
get_safe_backlog_item | read | Get one epic, feature or story with its SAFe planning (ART, PI, iteration and team, with names), kanban state and the states it can move to next, rank, sizing, latest WSJF score and recent WSJF history, and its backlog dependencies. |
update_safe_backlog_planning | write | Set an epic, feature or story's SAFe planning: ART, program increment, iteration, team, rank, story subtype (user or enabler), enabler kind (architectural, infrastructure, exploration, compliance), feature estimate and epic size. |
transition_safe_backlog_item | write | Move an epic, feature or story to another kanban state of its level (see list_safe_kanban_states, or next_states on get_safe_backlog_item). |
list_safe_kanban_states | read | List the portfolio kanban states for epics, features and stories (or one level): order, whether each is an initial or terminal state, WIP limit, and the states each one may move to next. |
add_backlog_dependency | write | Record a dependency between two backlog items: the first blocks (default), is related to, duplicates or is the parent of the second. |
remove_backlog_dependency | write, destructive | Remove a backlog dependency by its id (from get_safe_backlog_item or list_art_dependencies). |
record_wsjf_score | write | Score an epic, feature or story for Weighted Shortest Job First. |
get_wsjf_leaderboard | read | Rank an ART's epics, features or stories (default features) by their latest WSJF score, highest first, unscored last — the order to pull work in. |
#Inspect & Adapt and flow metrics
| Tool | Access | What it does |
|---|---|---|
list_inspect_adapt_sessions | read | List Inspect & Adapt sessions, most recent first, with their PI, facilitator, improvement item count and the predictability the web app last cached. |
get_inspect_adapt_session | read | Get one Inspect & Adapt session: its PI, system demo notes, facilitator, improvement items from the problem-solving workshop, and PI predictability computed now — per team and for the ART, actual over planned business value of committed objectives. |
create_inspect_adapt_session | write | Open the Inspect & Adapt session for a program increment, with the date it is held, optional system demo notes and a facilitator. |
add_improvement_item | write | Add an improvement item from the problem-solving workshop to an Inspect & Adapt session: the problem, its root cause and countermeasure, an owner, and the PI the fix is targeted at. |
update_improvement_item | write | Update an improvement item's problem, root cause, countermeasure, owner, target PI or status (open, in_progress, done, dropped). |
get_flow_metrics | read | Get an Agile Release Train's flow metrics: flow velocity, distribution, time, load and efficiency as stored period series, or one metric. |
recompute_flow_velocity | write | Recompute an Agile Release Train's weekly flow velocity: for each Monday-to-Sunday week, how many of its backlog items moved into a terminal kanban state. |
#Checklists
Company checklist settings, the group and template catalog, and checklists on individual work items.
#Config and catalog reads
| Tool | Access | What it does |
|---|---|---|
get_checklist_config | read | Read the company checklist framework configuration: whether it is enabled, the bypass and custom-group policy flags, and the required-groups matrix per work-item type. |
list_checklist_groups | read | List the company catalogue checklist groups (system and custom). |
list_checklist_templates | read | List the company checklist templates with their items. |
get_work_item_checklist | read | Read a work item's checklist: its groups with nested items and the overall/per-group completion status. |
#Catalog management
| Tool | Access | What it does |
|---|---|---|
create_checklist_group | write | Create a custom company-catalogue checklist group. |
update_checklist_group | write | Update a catalogue checklist group. |
delete_checklist_group | write | Delete a custom catalogue checklist group (and its templates). |
create_checklist_template | write | Create a checklist template that owns one catalogue group and a list of item labels. |
update_checklist_template | write | Update a checklist template. |
delete_checklist_template | write | Delete a checklist template and its items. |
#Per work item
| Tool | Access | What it does |
|---|---|---|
add_checklist_item | write | Add a checklist item to a group on a work item. |
update_checklist_item | write | Update a checklist item's label (text only). |
delete_checklist_item | write | Delete a checklist item from a work item. |
complete_checklist_item | write | Mark a checklist item complete or incomplete. |
add_checklist_group | write | Attach an existing catalogue checklist group (by its catalogue group id) to a work item. |
create_custom_checklist_group | write | Create a one-off custom checklist group directly on a work item (not from the catalogue). |
rename_checklist_group | write | Rename a checklist group on a work item (this work item only — never the shared catalogue). |
delete_work_item_checklist_group | write | Remove a checklist group (and its items) from a work item. |
reorder_checklist_groups | write | Set the display order of a work item's checklist groups. |
add_checklist_group_from_template | write | Copy a checklist template (its group and all items) onto a work item as an independent group. |
#What these tools are good at
🔍Cross-project questions
"What's overdue across everything I own?", tedious by hand, one call for an assistant.
🏃Sprint mechanics
Plan, start and close sprints, and move work in and out of them, without clicking through the board.
🧪QA authoring
Turn a spec into scenarios, cases and ordered steps, then file defects against them.
✅Checklist hygiene
Apply a template to a work item and tick items off as the conversation progresses.
📝Capture from context
Turn a chat thread or a code review into a backlog, epic to subtask.
⏱Time reconstruction
"Log yesterday's work from my commits", reads git, writes timelogs.
#Limits worth knowing
- Scope failures happen at call time. The assistant sees the whole catalog
regardless of what you granted; a tool you did not approve returns
403naming the scope it wanted. - No bulk endpoints. Creating twenty tasks is twenty calls, each counting against the rate limit.
- No idempotency key. A retried create makes a second record. If a write appears to fail, have the assistant search before retrying.
- Some tools are v4-only. Sprints and test scenarios are not available on older workspaces.
- Not everything in the REST API is a tool. The domains above are the MCP surface; anything else is REST only.