Skip to main content
Glama
Sign In
TFS MCP Server

TFS MCP Server

by abdulrahman-nabil99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

TFS MCP Server

An MCP server (Node.js) that bridges Claude Code with an on-premise Azure DevOps Server / TFS collection (set your own collection URL via TFS_ORG_URL).

Auth: Personal Access Token (PAT).

1. Generate a PAT

In TFS: top-right avatar → Security / Personal Access Tokens → New Token. Grant scopes: Work Items (Read & Write) and Code (Read & Write).

Related MCP server: tfs-mcp-server

2. Configure environment

Variable

Required

Description

TFS_ORG_URL

yes

Collection URL, e.g. https://your-tfs-server/YourCollection

TFS_PAT

yes

The personal access token

TFS_PROJECT

no

Default project name (so you don't pass it every call)

TFS_API_VERSION

no

REST API version (default 7.1; try 6.0 if a call 404s)

TFS_IGNORE_SSL

no

true to skip TLS cert verification (use if the internal CA isn't trusted)

3. Register with Claude Code

claude mcp add tfs \
  --env TFS_ORG_URL=https://your-tfs-server/YourCollection \
  --env TFS_PAT=<your-pat> \
  --env TFS_PROJECT=<your-default-project> \
  --env TFS_IGNORE_SSL=true \
  -- node /absolute/path/to/tfs-mcp-server/src/index.js

Or add to .mcp.json / settings manually (see mcp.example.json).

Tools

General

  • tfs_list_projects

Work Items

  • tfs_query_work_items — run a WIQL query

  • tfs_get_work_item

  • tfs_create_work_item

  • tfs_update_work_item

  • tfs_add_work_item_comment

Git / Pull Requests

  • tfs_list_repos

  • tfs_list_branches

  • tfs_list_commits

  • tfs_list_pull_requests

  • tfs_get_pull_request

  • tfs_create_pull_request

Available Tools

12 tools
tfs_add_work_item_commentC

Add a comment to a work item.

Inputs: id (required), text (required), project.

tfs_create_pull_requestC

Create a pull request from a source branch to a target branch.

Inputs: title (required), repositoryId (required), sourceBranch (required), targetBranch (required), +2 more.

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.

Inputs: type (required), title (required), fields, project.

tfs_get_pull_requestC

Get details of a single pull request.

Inputs: repositoryId (required), pullRequestId (required), project.

tfs_get_work_itemA

Get a single work item with all its fields by ID.

Inputs: id (required).

tfs_list_branchesC

List branches of a Git repository.

Inputs: repositoryId (required), project.

tfs_list_commitsC

List recent commits for a Git repository, optionally filtered by branch.

Inputs: repositoryId (required), top, branch, project.

tfs_list_projectsA

List all team projects in the TFS collection.

Inputs: no named parameters.

tfs_list_pull_requestsC

List pull requests for a repository.

Inputs: repositoryId (required), top, status, project.

tfs_list_reposA

List Git repositories in a project (or the whole collection if no project).

Inputs: project.

tfs_query_work_itemsA

Run a WIQL query and return matching work items (id + key fields). Provide a full WIQL SELECT statement.

Inputs: wiql (required), top, project.

tfs_update_work_itemC

Update fields on an existing work item by ID.

Inputs: id (required), fields (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.5/5.0

    Scored across 12 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers