A
licenseA
qualityC
maintenanceAn MCP server that exposes 41 Azure DevOps tools to AI assistants, enabling management of pipelines, repositories, pull requests, releases, work items, test management, and wikis through natural language.
41
MIT
tool-disco
by egoughnour
Related Servers
Alternatives to tool-disco
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to interact with Azure DevOps projects, work items, repositories, pipelines, wikis, and more via 21 tools.21-
- FlicenseNot gradedqualityCmaintenanceSelf-evolving MCP server that automatically discovers, generates, and registers new tools on demand using AI, enabling dynamic tool expansion without manual intervention.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to automatically discover, install, and learn to use new tools without manual configuration.31 npm16MIT
- AlicenseAqualityBmaintenanceAn MCP server that exposes a curated database of generative AI tools as four tools an AI assistant can query directly, enabling searches without relying on model knowledge.41MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
TDQS
A3.7/5.0
Scored across 8 tools
Disambiguation3/5
Most tools have clear roles, but discover_tools and plan_capabilities_for_goal both address goal-driven tool selection, which could cause misselection. test_composition adds another layer of ambiguity about how it relates to discover_tools.
Naming Consistency5/5
All tools follow a consistent verb_noun snake_case pattern (e.g., discover_tools, ingest_repo, invoke_planned_tool). The naming convention is uniform and predictable.
Tool Count5/5
8 tools is well within the ideal 3-15 range, covering distinct stages of the discovery workflow without excess. Each tool appears to serve a necessary function.
Completeness4/5
The set covers discovery, ingestion, planning, invocation, and stats, forming a cohesive workflow. However, it lacks explicit management of registered candidates beyond Azure DevOps scanning, which could be a minor gap.
Maintenance
ActivityInactive
ResponsivenessNo issues