MCP Github Project Manager vs MCP Server Azure Devops
A side-by-side look at the MCP Github Project Manager and MCP Server Azure Devops MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Github Project Manager for version control work as a local process; choose MCP Server Azure Devops for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Github Project Manager when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GITHUB_TOKEN, GITHUB_OWNER, GITHUB_REPO. - You want tools like
manage_project, manage_issues, manage_prs.
Choose MCP Server Azure Devops when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
AZURE_DEVOPS_ORG_URL, AZURE_DEVOPS_AUTH_METHOD, AZURE_DEVOPS_PAT, AZURE_DEVOPS_DEFAULT_PROJECT, AZURE_DEVOPS_API_VERSION, AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET. - You want tools like
get_me, list_organizations, list_projects.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 68/100 · Great | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | other |
| Pricing | Not declared | Free |
| Required env vars | GITHUB_TOKENGITHUB_OWNERGITHUB_REPO | AZURE_DEVOPS_ORG_URLAZURE_DEVOPS_AUTH_METHODAZURE_DEVOPS_PATAZURE_DEVOPS_DEFAULT_PROJECTAZURE_DEVOPS_API_VERSIONAZURE_TENANT_IDAZURE_CLIENT_IDAZURE_CLIENT_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 105 | 399 |
| Directory activity | 1 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 20 | 33 |
| Full listing | View MCP Github Project Manager | View MCP Server Azure Devops |
Tools & capabilities
MCP Github Project Manager tools 20
manage_projectManage GitHub Projects (v2): create, list, get, update, delete projects; manage readme, fields, views, items; handle templates and link to repos/teams. Use the `action` field to select the operation.manage_issuesManage GitHub Issues: create, list, get, update issues; manage comments and drafts; search with advanced filters; manage sub-issues. Use the `action` field to select the operation.manage_prsManage Pull Requests: create, get, list, update, merge PRs; list and create reviews. Use the `action` field to select the operation.manage_milestonesManage Milestones: create, list, update, delete milestones; get metrics; find overdue and upcoming milestones. Use the `action` field to select the operation.manage_sprintsManage Sprints: create, list, update sprints; get current sprint; add/remove issues; get metrics and plan. Use the `action` field to select the operation.manage_labelsManage repository Labels: create and list labels. Use the `action` field to select the operation.manage_automationManage Project Automations: list, get and delete the automation workflows of a GitHub project. Use the `action` field to select the operation.manage_iterationsManage Project Iterations: get configuration, current iteration, items; find by date; assign items. Use the `action` field to select the operation.manage_eventsManage Events: subscribe to project events, get recent events, replay events. Use the `action` field to select the operation.manage_status_updatesManage project Status Updates: create, list, and get status updates. Use the `action` field to select the operation.ai_generateAI-powered generation: generate/enhance/parse PRDs, add features, get next tasks, analyze complexity, expand tasks, create traceability matrices. Use the `action` field to select the operation.ai_analyzeAI-powered analysis: enrich issues (single/bulk), triage issues, schedule triaging, suggest labels, detect duplicates, find related issues. Use the `action` field to select the operation.- +8 more on the listing page
MCP Server Azure Devops tools 33
get_meGet details of the authenticated user (id, displayName, email) (Azure DevOps Services only)list_organizationsList all accessible organizations (Azure DevOps Services only)list_projectsList all projects in an organizationget_projectGet details of a specific projectget_project_detailsGet comprehensive details of a project including process, work item types, and teamslist_repositoriesList all repositories in a projectget_repositoryGet details of a specific repositoryget_repository_detailsGet detailed information about a repository including statistics and refsget_file_contentGet content of a file or directory from a repositoryget_repository_treeList a repository's file tree from any path and depthcreate_branchCreate a new branch from an existing onecreate_commitCommit multiple file changes to a branch using unified diffs or search/replace instructions- +21 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Github Project Manager
{
"mcpServers": {
"mcp-github-project-manager": {
"command": "npx",
"args": [
"-y",
"mcp-github-project-manager"
],
"env": {
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE",
"GITHUB_OWNER": "YOUR_GITHUB_OWNER_HERE",
"GITHUB_REPO": "YOUR_GITHUB_REPO_HERE"
}
}
}
}
MCP Server Azure Devops
{
"mcpServers": {
"tiberriver256-mcp-server-azure-devops": {
"command": "npx",
"args": [
"-y",
"@tiberriver256/mcp-server-azure-devops"
],
"env": {
"AZURE_DEVOPS_ORG_URL": "YOUR_AZURE_DEVOPS_ORG_URL_HERE",
"AZURE_DEVOPS_AUTH_METHOD": "YOUR_AZURE_DEVOPS_AUTH_METHOD_HERE",
"AZURE_DEVOPS_PAT": "YOUR_AZURE_DEVOPS_PAT_HERE",
"AZURE_DEVOPS_DEFAULT_PROJECT": "YOUR_AZURE_DEVOPS_DEFAULT_PROJECT_HERE",
"AZURE_DEVOPS_API_VERSION": "YOUR_AZURE_DEVOPS_API_VERSION_HERE",
"AZURE_TENANT_ID": "YOUR_AZURE_TENANT_ID_HERE",
"AZURE_CLIENT_ID": "YOUR_AZURE_CLIENT_ID_HERE",
"AZURE_CLIENT_SECRET": "YOUR_AZURE_CLIENT_SECRET_HERE"
}
}
}
}
Frequently asked questions
MCP Github Project Manager is categorized under Version Control and uses a local stdio subprocess. MCP Server Azure Devops belongs to Version Control and uses a local stdio subprocess. Pick MCP Github Project Manager for version control work and MCP Server Azure Devops for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Github Project Manager has no declared pricing — check the project's own site. Auth: api key required. MCP Server Azure Devops is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-github-project-manager and tiberriver256-mcp-server-azure-devops as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Github Project Manager has a quality signal of 68/100 (Great) with 1 views, 0 installs and 105 GitHub stars. MCP Server Azure Devops has 67/100 (Great) with 7 views, 0 installs and 399 GitHub stars.