Skip to main content
Glama
fuseboxhq

devops-wrangler

by fuseboxhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
ado_configureB

Configure Azure DevOps connection with your PAT and organization URL

ado_statusA

Check current Azure DevOps configuration status

ado_projectsA

Manage Azure DevOps projects.

Actions:

  • list: List all projects in organization

  • set: Set active project (requires: project)

  • areas: List area paths in active project

ado_create_itemsA

Create work items in Azure DevOps with optional hierarchy (Epic > Feature > User Story > Task). Items are assigned to the configured Area Path (board). Use addToCurrentSprint=true to add items to the active sprint.

ado_query_itemsA

Query existing work items in the active Azure DevOps project

ado_update_itemB

Update a work item's fields (title, state, assignee, description, area path, sprint, story points)

ado_delete_itemA

Delete a work item (moves to recycle bin by default, use permanent=true for hard delete)

ado_link_itemA

Link a work item to another work item, pull request, commit, or branch

ado_commentsA

Manage work item comments.

Actions:

  • add: Add comment to work item (requires: id, text)

  • list: List comments on work item (requires: id, optional: limit)

Markdown Support: Azure DevOps comments support full markdown formatting including bold, italic, code, lists, headers, links, and code blocks.

ado_sprintsA

Manage sprints/iterations.

Actions:

  • list: List sprints for configured team (optional: timeframe)

  • set: Assign work item to sprint (requires: id, sprint)

  • create: Create a new sprint (requires: name, optional: startDate, finishDate, parent)

  • delete: Delete a sprint (requires: path, optional: reclassifyId)

ado_plansA

Manage delivery plans (roadmaps).

Actions:

  • list: List delivery plans in project

  • get: Get plan timeline details (requires: planId, optional: startDate, endDate)

ado_tagsA

Manage work item tags in Azure DevOps.

Actions:

  • list: List all tags in the project (no additional params)

  • add: Add tags to a work item (requires: id, tags)

  • remove: Remove tags from a work item (requires: id, tags)

  • query: Find work items by tag (requires: tag, optional: limit)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 12 tools

Disambiguation4/5

Most tools target distinct resources and actions, but there is minor overlap: sprints.set and update_item both assign work items to sprints, and tags.query partially overlaps with query_items. Descriptions clarify the intended use, so ambiguity is low.

Naming Consistency4/5

The ado_ prefix gives a consistent namespace, but naming patterns vary: some tools use verb_noun (create_items, update_item) while others are resource-only nouns with sub-actions (projects, comments, sprints, plans, tags). This is a minor inconsistency, though names remain predictable and readable.

Tool Count5/5

12 tools is well within the ideal range for a domain-specific server. Each tool covers a meaningful area of Azure DevOps, and the count feels balanced without unnecessary bloat or missing essentials.

Completeness4/5

The surface covers configuration, project selection, work item lifecycle (create, query, update, delete), linking, comments, sprints, tags, and plans. Minor gaps exist, such as lack of project creation/deletion and explicit single-item fetch, but these are not critical for the apparent focus on work item management.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources