Gitlab Public vs MCP Server Azure Devops

A side-by-side look at the Gitlab Public 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.

Gitlab Public logoGitlab PublicVersion Control · Local subprocess (stdio)GitLab Public MCP — wraps the GitLab REST API v4 (public endpoints, no auth)60GoodAuth: not declaredMCP Server Azure Devops logoMCP Server Azure DevopsVersion Control · Local subprocess (stdio)Azure DevOps integration for repository management, work items, and pipelines.67GreatAuth: other

Verdict: choose Gitlab Public 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?

Gitlab Public logoChoose Gitlab Public when

  • You need dedicated capabilities in the Version Control domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search_projects, get_project, search_issues.
Explore Gitlab Public

MCP Server Azure Devops logoChoose 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_PAT.
  • You want tools like get_me, list_organizations, list_projects.
Explore MCP Server Azure Devops

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGitlab Public logoGitlab PublicMCP Server Azure Devops logoMCP Server Azure Devops
CategoryVersion ControlVersion Control
Quality signal60/100 · Good67/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredother
PricingNot declaredFree
Required env varsNone listedAZURE_DEVOPS_ORG_URLAZURE_DEVOPS_PAT
Verified ownerCommunity listingCommunity listing
GitHub stars1397
Directory activity 3 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools333

Tools & capabilities

Gitlab Public tools 3

  • search_projectsSearch public GitLab projects by keyword, sorted by popularity. Returns project ID, name, description, star count, fork count, open issues, and web URL.
  • get_projectGet full details for a public GitLab project by numeric ID or "namespace/project" path (e.g., "gitlab-org/gitlab"). Pass the path as written, with a plain slash — do not URL-encode it, the tool handles that internally. Returns name, description, stars, forks, default branch, topics, and last activity date.
  • search_issuesSearch issues across public GitLab projects by keyword. Returns issue title, state, author, labels, project ID, and direct URL.

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 organization
  • get_projectGet details of a specific project
  • get_project_detailsGet comprehensive details of a project including process, work item types, and teams
  • list_repositoriesList all repositories in a project
  • get_repositoryGet details of a specific repository
  • get_repository_detailsGet detailed information about a repository including statistics and refs
  • get_file_contentGet content of a file or directory from a repository
  • get_repository_treeList a repository's file tree from any path and depth
  • create_branchCreate a new branch from an existing one
  • create_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.

Gitlab Public

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gitlab-public": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-gitlab-public"
      ]
    }
  }
}

MCP Server Azure Devops

mcpServers (Claude Desktop / Cursor)
{
  "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_PAT": "YOUR_AZURE_DEVOPS_PAT_HERE"
      }
    }
  }
}

Frequently asked questions

Gitlab Public 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 Gitlab Public 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.

Gitlab Public has no declared pricing — check the project's own site. 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 gitlab-public 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, Gitlab Public has a quality signal of 60/100 (Good) with 3 views, 0 installs and 1 GitHub stars. MCP Server Azure Devops has 67/100 (Great) with 4 views, 0 installs and 397 GitHub stars.