Xcode Instruments CLI

Created By
nzrskya year ago
Overview

What is XCTools MCP Server?

XCTools MCP Server is a Model Context Protocol (MCP) server that provides structured access to Xcode development tools including xcrun, xcodebuild, and xctrace.

How to use XCTools MCP Server?

To use XCTools MCP Server, you can install it using various methods such as uvx, local development installation, or building from source. After installation, you can run the server and configure it for use with various clients like Claude Desktop or VS Code.

Key features of XCTools MCP Server?

  • Complete access to Xcode toolchain through xcrun
  • Project building and testing capabilities with xcodebuild
  • Performance analysis using xctrace (Instruments)
  • Comprehensive error handling with detailed messages
  • Cross-platform compatibility (macOS with Xcode installed)

Use cases of XCTools MCP Server?

  1. Finding paths to development tools like clang and swift.
  2. Building Xcode projects or workspaces.
  3. Running tests for projects/workspaces.
  4. Recording performance traces using Instruments.
  5. Managing SDKs and build destinations.

FAQ from XCTools MCP Server?

  • What are the prerequisites for using XCTools MCP Server?

You need Python 3.13+, Xcode with Command Line Tools installed, and optionally uvx for easier execution.

  • Can I use XCTools MCP Server on non-macOS systems?

No, XCTools MCP Server is designed specifically for macOS with Xcode installed.

  • How do I troubleshoot common issues?

Common issues include missing Xcode Command Line Tools, permission errors, and tool not found errors. Ensure Xcode is properly installed and configured.

Server Config

{
  "mcpServers": {
    "xcinstruments": {
      "command": "uvx",
      "args": [
        "xctools-mcp-server"
      ],
      "env": {}
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nzrsky
Star
-
Language
-
License
-
Category

Recommend Servers

View All
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