Xcforge MCP Server

95 MCP tools for iOS — build, test, simulate, automate UI, capture, and diagnose.

Local serverstdio

What is the Xcforge MCP server?

If you already use Xcforge, the xcforge mcp server is the piece that lets your assistant work with it directly. 95 MCP tools for iOS — build, test, simulate, automate UI, capture, and diagnose.

What the server does

An MCP server and CLI for iOS development — build, test, automate, and diagnose from any AI agent or terminal.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Category — Count
  • Build — 6
  • Test — 7
  • Simulator — 18
  • Screenshots — 3
  • Logs — 4
  • Console — 3
  • SPM — 5
  • Accessibility — 5
  • Diagnosis — 10
  • Session — 3
  • Homebrew — The Homebrew tool exposed by this server

Installation

skills on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: XCFORGE_WDA_DIR. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • macOS 13+ - Xcode 15+ - Swift 6.0+ (source builds only) - WebDriverAgent (UI automation only — see UI Automation Setup) ---

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Xcforge's toolset — Category, Build, Test and 11 more — is a fair guide to whether it matches your workflow. It is maintained by justinthevoid; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Xcforge.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CategoryCount
Build6
Test7
Simulator18
Screenshots3
Logs4
Console3
SPM5
Accessibility5
Diagnosis10
Session3
HomebrewThe Homebrew tool exposed by this server.
CursorFile: .cursor/mcp.json in your project root (or ~/.cursor/mcp.json for global)
WindsurfThe Windsurf tool exposed by this server.

How to install the Xcforge MCP server

{
  "mcpServers": {
    "xcforge": {
      "command": "npx",
      "args": ["-y", "skills"],
      "env": {
        "XCFORGE_WDA_DIR": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • macOS 13+ - Xcode 15+ - Swift 6.0+ (source builds only) - WebDriverAgent (UI automation only — see UI Automation Setup) ---
VariableDescriptionRequired
XCFORGE_WDA_DIRFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Xcforge to Category.
  • Use Xcforge to Build.
  • Use Xcforge to Test.

Frequently asked questions

It connects Xcforge to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Category, Build, Test, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Xcforge directly.