Ext Ops Panel
Open dashboard
Comparison

xcode-cloud vs com.xcodebuildmcp/XcodeBuildMCP

xcode-cloud is a plugin bundle for AI coding tools published by JamalBelilet. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.xcodebuildmcp/XcodeBuildMCP is an MCP server published by xcodebuildmcp.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacexcode-cloudcom.xcodebuildmcp/XcodeBuildMCP
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.7.0
Downloads/month (npm): 265 328
Downloads/week (npm): 69 386
Forks (GitHub): 323
Stars (GitHub): 6 475
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

xcode-cloud vs com.xcodebuildmcp/XcodeBuildMCP
Factxcode-cloudcom.xcodebuildmcp/XcodeBuildMCP
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)6 475 (better)
Forks (GitHub) (differs)0 (worse)323 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (xcode-cloud)On your machine (xcodebuildmcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 0
Hooks it runs (differs)1Not published
Parts of the bundle (differs)12Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/jamalbelilet/xcode-cloud-plugingithub.com/getsentry/xcodebuildmcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

xcode-cloud

In its own words, on Claude Code: claude-plugins-community:

Apple Xcode Cloud CI/CD integration. Monitor builds, diagnose failures, trigger workflows, and manage your iOS/macOS CI pipeline directly from Claude Code. Provides 21 MCP tools, 7 skills, and 3 specialized agents for build analysis, pipeline optimization, and flaky test detection, all powered by the App Store Connect API.

com.xcodebuildmcp/XcodeBuildMCP

In its own words, on Official MCP Registry:

XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.

How to run each

xcode-cloud As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install xcode-cloud@claude-community

com.xcodebuildmcp/XcodeBuildMCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio xcodebuildmcp -- npx -y xcodebuildmcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of xcode-cloud publish no settings it asks for, so we do not compare settings.

What it can do: xcode-cloud · What it can do: com.xcodebuildmcp/XcodeBuildMCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built