Appwrite MCP vs Azure DevOps (ADO)

A side-by-side look at the Appwrite MCP 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.

Appwrite MCP logoAppwrite MCPDeveloper Tools · Remote HTTP/SSEOfficial Appwrite MCP server. Connect via hosted OAuth at https://mcp.appwrite.io/ (no API keys) or self-host with a project API key to manage databases, auth, users, functions, storage, messaging, and more.77GreatAuth: oauth 2.0
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 Appwrite MCP 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?

Appwrite MCP logoChoose Appwrite MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Appwrite MCP

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.

SpecAppwrite MCP logoAppwrite MCP
A
Azure DevOps (ADO)
CategoryDeveloper ToolsDeveloper Tools
Quality signal77/100 · Great55/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthOAuth 2.0Not declared
PricingFreeFree
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars732,062
Directory activity 4 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Appwrite MCP 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.

Appwrite MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "appwrite-mcp": {
      "url": "https://mcp.appwrite.io/"
    }
  }
}

Azure DevOps (ADO)

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

Frequently asked questions

Appwrite MCP 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 Appwrite MCP 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.

Appwrite MCP is listed as free. Auth: oauth 2.0. 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 appwrite-mcp and azure-devops-ado as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Appwrite MCP has a quality signal of 77/100 (Great) with 4 views, 0 installs and 73 GitHub stars. Azure DevOps (ADO) has 55/100 (Good) with 6 views, 0 installs and 2,062 GitHub stars.