Azure DevOps (ADO) vs ShipSwift

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

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
ShipSwift logoShipSwiftDeveloper Tools · Remote HTTP/SSE40+ production-ready SwiftUI recipes for building full-stack iOS apps via MCP.65GreatAuth: not declared

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

Which MCP server should you choose?

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)

ShipSwift logoChoose ShipSwift when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like listRecipes, getRecipe, searchRecipes.
Explore ShipSwift

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
Azure DevOps (ADO)
ShipSwift logoShipSwift
CategoryDeveloper ToolsDeveloper Tools
Quality signal55/100 · Good65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2,0663,245
Directory activity 6 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
ToolsNot listed3

Tools & capabilities

Azure DevOps (ADO) tools

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

ShipSwift tools 3

  • listRecipesList production-ready SwiftUI code recipes. Each recipe is a complete, copy-paste-ready implementation — not a tutorial. Covers native iOS features (SwiftUI, Swift Charts, SpriteKit, Vision, AVFoundation, StoreKit 2, NavigationStack) and backend infrastructure (AWS CDK, Hono, Node.js, Cognito, DynamoDB). Categories: animations, charts, UI components, and full-stack modules including auth, camera, subscriptions, chat, and settings.
  • getRecipeGet a recipe by ID. Returns complete, copy-paste-ready Swift source code with architecture explanation and implementation steps. Module recipes may also include backend code (Hono/Node.js + AWS CDK).
  • searchRecipesSearch recipes by keyword across titles, descriptions, tags, and full source code. Use for any iOS, SwiftUI, or backend topic — e.g. subscription, authentication, camera, animation, chart, onboarding, paywall, infrastructure.

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.

Azure DevOps (ADO)

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

ShipSwift

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shipswift": {
      "url": "https://api.shipswift.app/mcp"
    }
  }
}

Frequently asked questions

Azure DevOps (ADO) is categorized under Developer Tools and uses a local stdio subprocess. ShipSwift belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Azure DevOps (ADO) for developer tools work and ShipSwift 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.

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

On AllMCPs, Azure DevOps (ADO) has a quality signal of 55/100 (Good) with 6 views, 0 installs and 2,066 GitHub stars. ShipSwift has 65/100 (Great) with 4 views, 0 installs and 3,245 GitHub stars.