RENAMED to drews-xcode-mcp - this compatibility package forwards to it
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"drews-xcode-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# xcode-mcp-server → drews-xcode-mcp **This package has been renamed to [drews-xcode-mcp](https://pypi.org/project/drews-xcode-mcp/).** With several projects named "xcode-mcp-server" in the wild — and Xcode itself now shipping a built-in MCP server — the old name had become ambiguous. Nothing breaks: installing this package pulls in `drews-xcode-mcp` and forwards the `xcode-mcp-server` command to it, so existing MCP client configurations keep working. Your settings carry over automatically (`~/.xcode-mcp-server` is renamed to `~/.drews-xcode-mcp` on first run), and `XCODEMCP_ALLOWED_FOLDERS` works as before. When convenient, update your MCP configuration to run `drews-xcode-mcp` instead. For Claude Code: ```bash claude mcp remove xcode-mcp-server claude mcp add --scope user --transport stdio -- drews-xcode-mcp `which uvx` drews-xcode-mcp ``` (If you have tool-permission allowlists tied to the old server name, you can keep the old name instead — replace the first `drews-xcode-mcp` after `--` (the server key) with `xcode-mcp-server`, leaving the package name at the end unchanged.) Source, documentation, and issues: https://github.com/drewster99/drews-xcode-mcp
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.