Xcode Mcp Server (drewster99)

Created By
drewster9910 months ago
An MCP (Model Context Protocol) server for controlling and interacting with Xcode from AI assistants and LLMs like Claude Code, Cursor, Claude Desktop, LM Studio, etc. This server significantly improves the build cycle. Now Claude (or your favorite tool) can directly command Xcode to build your project. Because Xcode is building it directly (rather than xcodebuild command-line or similar), the build happens exactly the same way as when you build it in Xcode. Xcode-mcp-server returns relevant build errors or warnings back to your coding tool (like Cursor or Claude Code), so the LLM sees exactly the same errors you do. Included tool functions here - you don't really need to know this info because your coding LLM will get this info (and more details) automatically, but I've included it here for the curious: - version - Returns xcode-mcp-server's version string - get_xcode_projects - Finds all .xcodeproj and .xcworkspace projects in the given search_path. If search_path is empty, all paths to which the tool has been granted access are searched - get_project_hierarchy - Returns the path hierarchy of the project or workspace - get_project_schemes - Returns a list of build schemes for the specified project - build_project - Commands Xcode to build. This is the workhorse that builds your project again and again, returning success or build errors - run_project - Commands Xcode to run your project - get_build_errors - Returns most recent build errors from the given project - clean_project - Cleans build
Overview

What is Xcode MCP Server?

Xcode MCP Server is a Model Context Protocol server designed to control and interact with Xcode from AI assistants and LLMs like Claude. It enhances the build cycle by allowing direct commands to Xcode, ensuring that builds occur in the same manner as when done manually in Xcode.

How to use Xcode MCP Server?

To use the Xcode MCP Server, set up the environment variable for allowed folders, start the server, and use natural language commands through your AI assistant to build, run, or manage your Xcode projects.

Key features of Xcode MCP Server?

  • Direct interaction with Xcode for building and running projects.
  • Retrieval of build errors and warnings.
  • Path-based security to restrict access to specified directories.
  • Support for multiple AI assistants like Claude and Cursor.

Use cases of Xcode MCP Server?

  1. Automating the build process for Xcode projects using AI.
  2. Quickly retrieving build errors to streamline debugging.
  3. Integrating Xcode with AI tools for enhanced development workflows.

FAQ from Xcode MCP Server?

  • Can I use Xcode MCP Server with any AI assistant?

Yes, it is compatible with various AI assistants like Claude and Cursor.

  • How do I set the allowed folders for security?

You can set the allowed folders using the environment variable XCODEMCP_ALLOWED_FOLDERS with a colon-separated list of absolute paths.

  • Is there a way to test the server locally?

Yes, you can test the server locally using the MCP Inspector interface.

Server Config

{
  "mcpServers": {
    "xcode-mcp-server": {
      "command": "uvx",
      "args": [
        "xcode-mcp-server"
      ]
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
drewster99
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago