Liminality vs Azure DevOps (ADO)

A side-by-side look at the Liminality and Azure DevOps (ADO) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

L
LiminalityDeveloper Tools · Remote HTTP/SSE
Reduces a request into grounded sub-questions, routes each to a real tool, returns a reusable route.44FairAuth: no auth required
A
Azure DevOps (ADO)Developer Tools · Local subprocess (stdio)
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.55GoodAuth: not declared

Verdict: choose Liminality for developer tools work over a hosted endpoint; choose Azure DevOps (ADO) for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

L
Choose Liminality when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Liminality

A
Choose Azure DevOps (ADO) when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore Azure DevOps (ADO)

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
L
Liminality
A
Azure DevOps (ADO)
CategoryDeveloper ToolsDeveloper Tools
Quality signal44/100 · Fair55/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNo auth requiredNot declared
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—2,066
Directory activity 0 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Liminality tools

No tool names declared yet. Check the project README from the listing page.

Azure DevOps (ADO) tools

No tool names declared yet. Check the project README from 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.

Liminality

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "liminality": {
      "url": "https://physea.ai/mcp"
    }
  }
}

Azure DevOps (ADO)

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "azure-devops-ado": {
      "command": "npx",
      "args": [
        "-y",
        "@azure-devops/mcp"
      ]
    }
  }
}

Frequently asked questions

Liminality is categorized under Developer Tools and uses a remote HTTP/SSE transport. Azure DevOps (ADO) belongs to Developer Tools and uses a local stdio subprocess. Pick Liminality for developer tools work and Azure DevOps (ADO) for developer tools.

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.

Liminality has no declared pricing — check the project's own site. Auth: no auth required. Azure DevOps (ADO) is listed as free. 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 liminality and azure-devops-ado as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Liminality has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Azure DevOps (ADO) has 55/100 (Good) with 6 views, 0 installs and 2,066 GitHub stars.