TFS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TFS_PAT | Yes | The personal access token | |
| TFS_ORG_URL | Yes | Collection URL, e.g. https://your-tfs-server/YourCollection | |
| TFS_PROJECT | No | Default project name (so you don't pass it every call) | |
| TFS_IGNORE_SSL | No | true to skip TLS cert verification (use if the internal CA isn't trusted) | |
| TFS_API_VERSION | No | REST API version (default 7.1; try 6.0 if a call 404s) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tfs_list_projectsA | List all team projects in the TFS collection. |
| tfs_query_work_itemsA | Run a WIQL query and return matching work items (id + key fields). Provide a full WIQL SELECT statement. |
| tfs_get_work_itemA | Get a single work item with all its fields by ID. |
| tfs_create_work_itemC | Create a work item. Pass the type (e.g. Bug, Task, User Story) and a map of field reference names to values. |
| tfs_update_work_itemC | Update fields on an existing work item by ID. |
| tfs_add_work_item_commentC | Add a comment to a work item. |
| tfs_list_reposA | List Git repositories in a project (or the whole collection if no project). |
| tfs_list_branchesC | List branches of a Git repository. |
| tfs_list_commitsC | List recent commits for a Git repository, optionally filtered by branch. |
| tfs_list_pull_requestsC | List pull requests for a repository. |
| tfs_get_pull_requestC | Get details of a single pull request. |
| tfs_create_pull_requestC | Create a pull request from a source branch to a target branch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.