Metadata-Version: 2.4
Name: xcode-mcp-server
Version: 1.3.17
Summary: RENAMED to drews-xcode-mcp - this compatibility package forwards to it
Project-URL: Homepage, https://github.com/drewster99/drews-xcode-mcp
Project-URL: Repository, https://github.com/drewster99/drews-xcode-mcp
Project-URL: Issues, https://github.com/drewster99/drews-xcode-mcp/issues
Author-email: Andrew Benson <db@nuclearcyborg.com>
License: MIT
License-File: LICENSE
Keywords: mcp,server,xcode
Classifier: Development Status :: 7 - Inactive
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Requires-Python: >=3.10
Requires-Dist: drews-xcode-mcp==1.3.17
Description-Content-Type: text/markdown

# 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
