This is the full catalogue of tools your AI assistant can call once it is connected. You never call these yourself — you ask in plain language and the assistant picks the tool — but knowing the names helps when you want to be precise ("use preview_convert_item_tree first") or when you read what the assistant did.
Every tool runs with your permissions in the organization the connection is bound to. A tool you lack permission for returns a refusal, which the assistant reports.
X-DevStride-Toolset: core sees only the everyday groups: workspace, resolvers, items, jobs, sub-items, workstreams, comments, boards, cycles, time entries, activity, quality, knowledge base, and the API gateway. The other groups below — marked hidden from core — are still callable by name and through invoke_api_operation; they are just not advertised, which saves the client tokens.| Tool | What it does |
|---|---|
whoami | Who you are, your teams, recent work, and an at-a-glance workload. The assistant should run this first; it also reports which organization the connection is bound to. |
get_workspace_context | A slim summary of the organization's configuration: item types, statuses, priorities, labels, custom fields, and default collections. |
get_organization_metadata | The same reference tables with optional projections. |
get_my_recent | Your recent boards, items, sub-tasks, and their parent hierarchies. |
get_workload | A member's open items split into due within 7 days and overdue. |
list_teams, list_members | Teams and members of the organization. Write tools accept a member's name, username, or email directly. |
get_work_type_hierarchy | The item-type tree. For each type, every permitted parent (parentTitles, parentWorkTypeIds, primary first), its children, and ancestorChains — one top-to-type chain per route through the hierarchy. |
find_parent_candidates | Given a child type, existing items of every permitted parent type that could hold it; the types are listed in parentWorkTypes. |
Translate names into the identifiers other tools need. Each returns one match or an ambiguous answer with candidates for the assistant to ask you about.
| Tool | Resolves |
|---|---|
resolve_board, resolve_board_folder | Board or board-folder name → board / folder |
resolve_team | Team name → team |
resolve_user | Name, username, or email → member |
resolve_label | Label name → label (optionally per item type) |
resolve_item | I123, F42, or a title → item or workstream |
| Tool | What it does |
|---|---|
search_items | Search and filter work items by board, team, assignee, labels, status, dates, and more. Can include items whose sub-task is assigned to you. |
get_item | One item by number, with IDs resolved to names. |
create_item | Create a work item; workType accepts a name such as "Story". For imported work, createdAt and creatorUsername record when and by whom it was really created (needs Backdate Item History). |
update_item | Update an item by number; omitted fields are unchanged. Refuses an F number and names the workstream tool instead. occurredAt records a status or board change as happening at a past time (needs Backdate Item History). |
bulk_update_items | Many updates in one call, up to 400 work units (one per item, plus one per relationship). Slow batches are queued as a job; larger ones are refused before anything changes. Accepts occurredAt per item, like update_item. |
replace_item_history | Replace an item's created date, optional creator, and whole status and board history in one call — the way to repair work imported flat on one day. Reports, the activity feed and the completed date are rebuilt; nobody is notified and no automation runs. Needs Backdate Item History and edit access. |
update_item_history_entry | Correct one thing in an item's history in place: its created date, its creator, or the date of one status or board change. Needs Backdate Item History and edit access. |
bulk_rerank_items | Rerank every item in a scope by a chosen field and direction. |
rank_item | Move one item above or below a sibling, or to a position, within a board, parent, or status. |
mark_done, reopen | Move an item to its board's done status, or back to its new status. |
move_to_board, move_to_cycle, reparent_item | Change an item's board, cycle ("current" works), or parent. |
add_relationship, remove_relationship | blocks, blocked_by, and related_to links. |
get_item_hierarchy | Ancestors and descendants of an item or workstream. |
summarize_item | Roll up a workstream or item from its descendants — quick counts or detailed status and scheduling buckets. |
copy_item | Copy an item, all fields or a chosen list. |
archive_item, unarchive_item | Reversible archive of an item or workstream (unarchive restores archived descendants by default). |
delete_item | Permanent. The assistant is told to prefer archive_item. |
preview_work_type_compatibility | Which types one item could change to, and which parent/child pairs would break. |
preview_convert_item_tree | Dry run of converting a parent and everything beneath it with a type mapping; reports tree size, broken pairs, and boards lacking a status for the new type. Changes nothing. |
convert_item_tree | Applies the mapping to the whole tree, all or nothing. Trees over 200 items are refused. Needs edit access to every item. |
| Tool | What it does |
|---|---|
get_job | Poll a queued job (a large bulk update, an applied template) until it is done, then read its output and per-item errors. |
| Tool | What it does |
|---|---|
list_sub_items | Every sub-task of one item. |
search_sub_items | Sub-tasks across items by text, assignee, author, parent, or date. |
get_sub_item, create_sub_item, update_sub_item, delete_sub_item | Read and manage a single sub-task. |
| Tool | What it does |
|---|---|
create_workstream | Create a workstream, optionally nested under another. |
update_workstream | Update a workstream by its F number. |
archive_workstream, unarchive_workstream | Reversible archive. |
delete_workstream | Permanent. Prefer archiving. |
The older *_folder names were removed on October 10, 2026; use these tools instead.
| Tool | What it does |
|---|---|
add_comment, reply_to_comment | Post a comment or reply, with @mentions. visibility is internal by default; public reaches a Service Desk requester and needs Send Public Replies. |
list_comments | An item's comments, including visibility and, on tickets, the customer author and delivery state. |
update_comment, delete_comment | Replace or delete a comment. A delivered public comment cannot be edited. |
react_to_comment, unreact_to_comment | Emoji reactions. |
| Tool | What it does |
|---|---|
list_boards, get_board | Boards and their configuration. |
create_board, update_board | Create (needs a board folder and status collection; add a timebox for a cycle board) or update a board. |
archive_board | Archive a board, moving its items to another board or archiving in place. |
delete_board | Permanent. Prefer archiving. |
create_board_folder, update_board_folder | The sidebar groupings boards live in. |
| Tool | What it does |
|---|---|
list_cadences, list_timeboxes | Cadences (recurring schedules) and the cycles within them. |
current_cycle | The cycle(s) running today, with their boards. |
create_cadence, update_cadence | Define or change a cadence. |
create_timebox, update_timebox, delete_timebox | Add, change, or permanently remove a cycle. |
| Tool | What it does |
|---|---|
start_time_entry, stop_time_entry, get_active_time_entry | Run and check a timer. |
add_time_entry | Log a closed entry with hours against an item or workstream. |
update_time_entry, delete_time_entry | Edit or permanently delete an entry. |
find_time_entries | Search entries by person, item, or date range. |
| Tool | What it does |
|---|---|
get_item_activity | The activity log of an item or other record. |
list_notifications, update_notification | Your in-app notifications; mark read or saved. |
| Tool | What it does |
|---|---|
devstride_help | A grouped catalogue of prompts you can ask. Good first call. |
my_items_quality | Your assigned items missing descriptions, estimates, points, effort, or logged time. |
board_quality | A board's health: status distribution, deadline pressure, gaps. |
| Tool | What it does |
|---|---|
find_kb_articles, search_kb_articles | Browse by state and category, or ranked full-text search with snippets. |
get_kb_article | One article with its body and editor link. |
create_kb_article, update_kb_article | Create a draft; edit title, body, category, or visibility. |
publish_kb_article, unpublish_kb_article, archive_kb_article, unarchive_kb_article | Move an article through its lifecycle. The first publish mints its permanent slug; unarchive returns it to draft. |
set_kb_article_audience | Which customer companies see the article on the portal. |
set_kb_article_comments_enabled | Switch an article's customer comment thread on or off. |
list_kb_article_comments, add_kb_article_comment, reply_to_kb_article_comment, resolve_kb_article_comment, unresolve_kb_article_comment | Read and take part in an article's review threads. Comments are internal notes unless you ask for a public one. |
list_kb_categories, create_kb_category, update_kb_category, delete_kb_category | Manage the category tree. Deleting a category re-parents its children and leaves articles uncategorized. |
list_kb_article_revisions, get_kb_article_revision, restore_kb_article_revision | Version history, one revision's content, and a restore of title and body. |
Publishing, archiving, audience, the comment switch, and category edits need Publish knowledge-base articles; commenting needs Comment on knowledge-base articles.
| Tool | What it does |
|---|---|
list_roadmaps, get_roadmap, create_roadmap, update_roadmap, delete_roadmap | Roadmaps (the Gantt), with their initiatives, milestones, items, and scenarios. |
create_initiative, update_initiative, delete_initiative, rank_initiative | Initiatives on a roadmap and their order. |
add_item_to_initiative, rank_roadmap_item | Attach items or workstreams to an initiative and order them. |
create_milestone, update_milestone, delete_milestone | Dated markers on the timeline. |
| Tool | What it does |
|---|---|
list_item_templates, get_item_template | Templates you own or that are shared with you; view: "full" returns the definition tree. |
create_item_template, update_item_template, delete_item_template | Author, replace, or permanently delete a template. |
create_item_template_from_item | Capture an existing subtree as a template — the fastest way to author one. |
share_item_template | Share with users, teams, or the organization. |
preview_item_template, apply_item_template | Dry-run against a target, then create the whole tree under it (returns a job). |
find_item_template_references | Which templates reference a type, team, user, field, priority, label, or board — ask before deleting one. |
| Tool | What it does |
|---|---|
link_pull_request, unlink_pull_request | Attach or detach a GitHub pull request by URL, as on the item's GitHub tab. |
get_item_branches, get_item_commits | Branches and commits linked to an item. |
See GitHub.
| Tool | What it does |
|---|---|
get_velocity, get_throughput, get_cycle_metrics | Delivery metrics per cycle and over time. |
get_current_progress | A progress snapshot, optionally filtered. |
get_time_tracking_report | Logged time between two dates, grouped by user, item, sub-item, or raw entry. |
run_time_allocation_matrix | The monthly actual-time allocation matrix for an item hierarchy and date range. Each level names one or more item types (levels[].workTypeIds); a level with several types lists their rows side by side. |
| Tool | What it does |
|---|---|
upload_attachment, attach_uploaded_file | Two steps to attach a local file to an item or workstream. |
| Tool | What it does |
|---|---|
invite_members, update_member, remove_member, reset_member_mfa | Invite, change role or teams, reactivate or remove a member, reset their MFA. |
approve_join_request, decline_join_request | Pending requests to join. |
create_team, update_team, archive_team, unarchive_team | Teams. |
list_roles, get_role, list_permission_keys, create_role, update_role, delete_role, set_default_invite_role | Roles, their permission grants, and the default role for new members. |
Create, update, and delete tools for each configurable collection: statuses and status collections, priorities and priority collections, labels and label collections, custom fields, custom-field collections and form groups, estimate options and their collections, user label groups, and item request groups and forms. Item types have update_work_type, archive_work_type, update_work_type_tab_order, and update_work_type_sidebar_field_order. The older *_lane* names were removed on October 10, 2026; use the status tools instead.
| Tool | What it does |
|---|---|
list_github_installations, create_github_installation | GitHub App installations. |
list_slack_installations, delete_slack_installation | Slack workspace connection. |
list_teams_installations, delete_teams_installation | Microsoft Teams tenant connection (never tokens). |
list_integration_credentials, list_credential_accounts, update_integration_credential, disable_integration_credential | Jira and Azure DevOps credentials. |
list_integration_installations, create_integration_installation, disable_integration_installation, submit_integration_job | Jira and Azure DevOps installations and import jobs. |
get_database_credentials, generate_database_credentials, delete_database_credentials | The organization's read-only database credential. |
| Tool | What it does |
|---|---|
get_billing_customer, update_billing_details | Billing contact and address. |
list_payment_methods, check_payment_method_exists, set_default_payment_method, delete_payment_method | Cards on file. |
list_invoices | Billing history. |
| Tool | What it does |
|---|---|
list_api_operations | Every DevStride API operation, grouped by service, with an optional search. |
describe_api_operation | The exact input schema for one operation. |
invoke_api_operation | Call any operation by id. Unknown keys anywhere in the call are refused before it runs, naming the offending path. |
This is how the assistant reaches anything without a purpose-built tool. Unlike the tools above, the gateway sends your input as-is: it does not wrap plain text or resolve names, so the assistant should call describe_api_operation first.
Best Practices & Tips
Habits that make the DevStride MCP Server fast, accurate, and safe: start read-only, ask it to propose before it changes anything, refer to things by name, and keep the connection healthy.
Getting Started With Plugins
What DevStride plugins are, how to get one enabled for your organization, and how to hide a plugin's menu from a role.