A
licenseNot graded
qualityD
maintenanceEnables AI assistants to interact with Azure DevOps for managing work items, repositories, wikis, and automating development workflows.
MIT
tfs-mcp-server
by K3roru
Related Servers
Alternatives to tfs-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceEnables AI agents to interact with Azure DevOps through natural language, supporting work items, pull requests, sprints, boards, teams, repositories, and wiki pages.30-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query and interact with Azure DevOps data, including work items, projects, ticket statistics, and backlog information through natural language commands.8,052 npmMIT
- FlicenseAqualityCmaintenanceConnects Claude to on-premise TFS (Team Foundation Server) via REST API, enabling read/write of work items, backlogs, sprints, and pull requests without manual copy-paste.8-
- FlicenseNot gradedqualityFmaintenanceEnables LLMs and AI applications to interact with Azure DevOps Work Items, supporting queries, filtering, status updates, date management, effort tracking, descriptions, and comments through natural language.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Azure DevOps APIs for managing projects, work items, repositories, pull requests, and pipelines through natural language.18 npmMIT
TDQS
A3.9/5.0
Scored across 17 tools
Disambiguation4/5
Most tools target clearly distinct resources and actions, such as fetching a single work item vs. many, or reading file content vs. listing a directory. The main area of potential confusion is between the singular/plural comment tools, especially add_work_item_comment and add_comment_to_work_items, though their descriptions clarify the difference.
Naming Consistency4/5
Tool names mostly follow a consistent snake_case verb_noun pattern: list_, get_, update_, add_, run_, and search_. Minor deviations exist, notably add_comment_to_work_items vs. add_work_item_comment and get_current_identity, but overall the naming is predictable and readable.
Tool Count4/5
17 tools is slightly above the ideal range but reasonable for a server covering both work item management and Git repository file access. Each tool serves a distinct purpose, and the count reflects the breadth of the domain without feeling bloated.
Completeness3/5
The work item surface is strong for reading and updating, including bulk operations and comments, but there is no create_work_item or delete_work_item, which is a notable lifecycle gap. The Git side is also read-only, covering file/directory access but no branch, commit, or repository management operations.
Maintenance
ActivityMaintained
ResponsivenessNo issues