[Feature]: Compatibility with Claude Cowork

[pjcreath]

Feature Description

Something about the Claude Cowork sandboxes doesn't like the way XcodeBuildMCP handles configuration:

1. Cowork sessions don't inherit the claude_desktop_settings.json configuration, and there's not another obvious way to set env variables that apply to Cowork.
2. Cowork can see the .xcodebuildmcp/config.yaml file, but when it runs the /xcodebuildmcp skill it doesn't use that configuration for some reason.

As a result, the only workflow available in Claude Cowork is the default simulator.

Use Cases

• Iterative development and testing

Example Interactions

No response

[pjcreath]

One possible solution to the bootstrap problem:

{
  "mcpServers": {
    "XcodeBuildMCP": {
      "command": "xcodebuildmcp",
      "args": [
        "mcp"
      ],
      "env": {
        "XCODEBUILDMCP_ENABLED_WORKFLOWS": "macos,project-scaffolding,swift-package"
      }
    }
  }
}

This seems to allow use of the enabled workflows, but the LLM thinks they're disabled since it can't introspect its environment and the skill file says that they're disabled by default. So doctor doesn't work as expected, but the workflows do.

Another approach would be changing the working directory before launching the server, but I don't know of any way to tell Cowork to use its workspace as the working directory when doing so.