TFS MCP Server
Related Servers
Alternatives to TFS MCP Server
No user-submitted related servers found.
Related Servers
- 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-
- AlicenseBqualityBmaintenanceEnables Claude Code to interact with Azure DevOps Server on-premises (work items, pull requests, repositories) through secure, controlled, safe-by-default access with read-only mode and explicit write confirmations.22MIT
- FlicenseBqualityBmaintenanceEnables users to securely connect Claude Desktop to Azure DevOps for managing work items, metadata, comments, pull requests, and code reviews.15-
- FlicenseNot gradedqualityDmaintenanceConnects Azure DevOps work items to Claude Code via MCP, enabling fetching, listing, updating tickets and automating PR creation.-
- AlicenseAqualityAmaintenanceA local MCP server that connects Claude Desktop, Claude Code, and Claude Chat to your Azure DevOps organization, enabling querying work items, reviewing pull requests, triggering pipelines, searching code, managing test plans, and updating wikis using plain language.30MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Azure DevOps through Personal Access Token authentication. Supports work item management, wiki operations, project/repository listing, and build pipeline access through natural language.736 npmMIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource and action (e.g., query vs. get vs. create work items; list vs. get vs. create pull requests), with no overlapping purposes. The tool descriptions clearly differentiate them.
All tools follow a consistent 'tfs_verb_noun' pattern using snake_case (e.g., tfs_list_projects, tfs_create_work_item). The verbs are simple and align with standard CRUD operations, making the naming predictable.
With 12 tools covering projects, work items, and git repositories, the number is well-scoped for a TFS MCP server. Each tool serves a distinct purpose without unnecessary redundancy or bloat.
The tool set covers core workflows: CRUD for work items (except delete), PR lifecycle (list, get, create), and repository browsing. Minor gaps like work item deletion or branch/repo creation exist, but the surface is largely complete for common tasks.