drews-xcode-mcp 1.3.16b1__tar.gz

drews_xcode_mcp-1.3.16b1/.gitignore

@@ -0,0 +1,35 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+build/
+*.egg-info/
+
+# Virtual environments
+.env
+.venv
+env/
+venv/
+ENV/
+
+# IDE specific files
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# OS specific files
+.DS_Store
+Thumbs.db 
+
+# Claude
+.claude
+.claude/**
+
+# Test working directory (ephemeral test artifacts)
+test_projects/working/

drews_xcode_mcp-1.3.16b1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Andrew Benson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

drews_xcode_mcp-1.3.16b1/PKG-INFO

@@ -0,0 +1,208 @@
+Metadata-Version: 2.4
+Name: drews-xcode-mcp
+Version: 1.3.16b1
+Summary: Drew's MCP server for Xcode integration
+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 :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.10
+Requires-Dist: mcp[cli]>=1.7.0
+Requires-Dist: questionary>=2.0.0
+Requires-Dist: rich>=13.0.0
+Description-Content-Type: text/markdown
+
+# Drew's Xcode MCP Server (drews-xcode-mcp)
+
+[![PyPI](https://img.shields.io/pypi/v/drews-xcode-mcp.svg)](https://pypi.org/project/drews-xcode-mcp/)
+[![Python Versions](https://img.shields.io/pypi/pyversions/drews-xcode-mcp.svg)](https://pypi.org/project/drews-xcode-mcp/)
+[![Downloads](https://static.pepy.tech/badge/drews-xcode-mcp)](https://pepy.tech/project/drews-xcode-mcp)
+[![MCP](https://img.shields.io/badge/MCP-Server-blue)](https://modelcontextprotocol.io)
+[![macOS Only](https://img.shields.io/badge/platform-macOS-lightgrey)](https://www.apple.com/macos/)
+[![Xcode](https://img.shields.io/badge/Xcode-Required-blue)](https://developer.apple.com/xcode/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
+[![GitHub last commit](https://img.shields.io/github/last-commit/drewster99/drews-xcode-mcp)](https://github.com/drewster99/drews-xcode-mcp/commits)
+
+An MCP (Model Context Protocol) server that enables AI assistants to control and interact with Xcode for Apple platform development.
+
+> **Renamed from `xcode-mcp-server`.** With several unrelated projects sharing that
+> name — and Xcode itself now shipping a built-in MCP server — this project is now
+> `drews-xcode-mcp`. **Existing setups keep working:** the old PyPI name is a
+> compatibility package that forwards to this one, and all settings carry over.
+> When convenient, update your MCP configuration to run `drews-xcode-mcp` (keep
+> your existing server key/name so tool permissions are unaffected).
+
+## What It Does
+
+This server allows AI assistants (like Claude, Cursor, or other MCP clients) to:
+
+- **Discover and navigate** your Xcode projects and source files
+- **Build and run** iOS, macOS, tvOS, and watchOS applications
+- **Execute and monitor tests** with detailed results
+- **Debug build failures** by retrieving errors and warnings
+- **Capture console output** from running applications
+- **Take screenshots** of Xcode windows and iOS simulators
+- **Manage simulators** and view their status
+
+The AI can perform complete development workflows - from finding a project, to building it, running tests, debugging failures, and capturing results.
+
+## Requirements
+
+- **macOS** - This server only works on macOS
+- **Xcode** - Xcode must be installed
+- **Python 3.10+** - For running the server (uvx will fetch a compatible Python automatically if your system Python is older)
+
+## Security
+
+The server implements path-based security to control which directories are accessible:
+
+- **With restrictions:** Set `XCODEMCP_ALLOWED_FOLDERS=/path1:/path2:/path3` to limit access to specific directories
+- **Default:** If not specified, allows access to your home directory (`$HOME`)
+
+Security requirements:
+- All paths must be absolute (starting with `/`)
+- No `..` path components allowed
+- All paths must exist and be directories
+
+## Setup
+
+First, ensure `uv` is installed (required for all methods below):
+```bash
+which uv || brew install uv
+```
+
+### 1. Claude Code (Recommended)
+
+```bash
+claude mcp add --scope user --transport stdio -- drews-xcode-mcp `which uvx` drews-xcode-mcp
+```
+
+To run a specific version, use:
+```bash
+# Example: How to run v1.3.0b6
+claude mcp add --scope user --transport stdio -- drews-xcode-mcp `which uvx` drews-xcode-mcp==1.3.0b6
+```
+
+That's it! Claude Code handles the rest automatically.
+
+### 2. Claude Desktop
+
+Edit your Claude Desktop config file (`~/Library/Application Support/Claude/claude_desktop_config.json`):
+
+```json
+{
+    "mcpServers": {
+        "drews-xcode-mcp": {
+            "command": "uvx",
+            "args": [
+                "drews-xcode-mcp"
+            ]
+        }
+    }
+}
+```
+
+If you'd like to allow only certain projects or folders to be accessible by drews-xcode-mcp, add the `env` option, with a colon-separated list of absolute folder paths, like this:
+
+```json
+{
+    "mcpServers": {
+        "drews-xcode-mcp": {
+            "command": "uvx",
+            "args": [
+                "drews-xcode-mcp"
+            ],
+            "env": {
+                "XCODEMCP_ALLOWED_FOLDERS": "/Users/andrew/my_project:/Users/andrew/Documents/source"
+            }
+        }
+    }
+}
+```
+
+### 3. Cursor AI
+
+In Cursor: Settings → Tools & Integrations → + New MCP Server
+
+Or edit `~/.cursor/mcp.json` directly:
+
+```json
+{
+    "mcpServers": {
+        "drews-xcode-mcp": {
+            "command": "uvx",
+            "args": ["drews-xcode-mcp"]
+        }
+    }
+}
+```
+
+**Optional:** Add folder restrictions with an `env` section (same format as Claude Desktop above).
+
+## Usage
+
+Once configured, simply ask your AI assistant to help with Xcode tasks:
+
+- "Find all Xcode projects in my home directory"
+- "Build the project at /path/to/MyProject.xcodeproj"
+- "Run tests for this project and show me any failures"
+- "What are the build errors in this project?"
+- "Show me the directory structure of this project"
+- "Take a screenshot of the Xcode window"
+
+Most tools work with paths to `.xcodeproj` or `.xcworkspace` files, or with regular directory paths for browsing and navigation.
+
+## Advanced Configuration
+
+### Command Line Arguments
+
+When running the server directly (for development or custom setups), these options are available:
+
+**Build output control:**
+- `--no-build-warnings` - Show only errors, exclude warnings
+- `--always-include-build-warnings` - Always show warnings (default)
+
+**Notifications:**
+- `--show-notifications` - Enable macOS notifications for operations
+- `--hide-notifications` - Disable notifications (default)
+
+**Access control:**
+- `--allowed /path` - Add allowed folder (can be repeated)
+
+Example:
+```bash
+drews-xcode-mcp --no-build-warnings --show-notifications --allowed ~/Projects
+```
+
+**Note:** When using MCP clients (Claude, Cursor), configure these via the `env` section in your client's config file instead.
+
+## Development
+
+The server is built with FastMCP and uses AppleScript to communicate with Xcode.
+
+### Local Testing
+
+Test with MCP Inspector:
+
+```bash
+export XCODEMCP_ALLOWED_FOLDERS=~/Projects
+mcp dev drews_xcode_mcp/__main__.py
+```
+
+This opens an inspector interface where you can test tools directly. Provide paths as quoted strings: `"/Users/you/Projects/MyApp.xcodeproj"`
+
+## Limitations
+
+- AppleScript syntax may need adjustments for specific Xcode versions
+- Some operations require the project to be open in Xcode first

drews_xcode_mcp-1.3.16b1/README.md

@@ -0,0 +1,184 @@
+# Drew's Xcode MCP Server (drews-xcode-mcp)
+
+[![PyPI](https://img.shields.io/pypi/v/drews-xcode-mcp.svg)](https://pypi.org/project/drews-xcode-mcp/)
+[![Python Versions](https://img.shields.io/pypi/pyversions/drews-xcode-mcp.svg)](https://pypi.org/project/drews-xcode-mcp/)
+[![Downloads](https://static.pepy.tech/badge/drews-xcode-mcp)](https://pepy.tech/project/drews-xcode-mcp)
+[![MCP](https://img.shields.io/badge/MCP-Server-blue)](https://modelcontextprotocol.io)
+[![macOS Only](https://img.shields.io/badge/platform-macOS-lightgrey)](https://www.apple.com/macos/)
+[![Xcode](https://img.shields.io/badge/Xcode-Required-blue)](https://developer.apple.com/xcode/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+
+[![GitHub last commit](https://img.shields.io/github/last-commit/drewster99/drews-xcode-mcp)](https://github.com/drewster99/drews-xcode-mcp/commits)
+
+An MCP (Model Context Protocol) server that enables AI assistants to control and interact with Xcode for Apple platform development.
+
+> **Renamed from `xcode-mcp-server`.** With several unrelated projects sharing that
+> name — and Xcode itself now shipping a built-in MCP server — this project is now
+> `drews-xcode-mcp`. **Existing setups keep working:** the old PyPI name is a
+> compatibility package that forwards to this one, and all settings carry over.
+> When convenient, update your MCP configuration to run `drews-xcode-mcp` (keep
+> your existing server key/name so tool permissions are unaffected).
+
+## What It Does
+
+This server allows AI assistants (like Claude, Cursor, or other MCP clients) to:
+
+- **Discover and navigate** your Xcode projects and source files
+- **Build and run** iOS, macOS, tvOS, and watchOS applications
+- **Execute and monitor tests** with detailed results
+- **Debug build failures** by retrieving errors and warnings
+- **Capture console output** from running applications
+- **Take screenshots** of Xcode windows and iOS simulators
+- **Manage simulators** and view their status
+
+The AI can perform complete development workflows - from finding a project, to building it, running tests, debugging failures, and capturing results.
+
+## Requirements
+
+- **macOS** - This server only works on macOS
+- **Xcode** - Xcode must be installed
+- **Python 3.10+** - For running the server (uvx will fetch a compatible Python automatically if your system Python is older)
+
+## Security
+
+The server implements path-based security to control which directories are accessible:
+
+- **With restrictions:** Set `XCODEMCP_ALLOWED_FOLDERS=/path1:/path2:/path3` to limit access to specific directories
+- **Default:** If not specified, allows access to your home directory (`$HOME`)
+
+Security requirements:
+- All paths must be absolute (starting with `/`)
+- No `..` path components allowed
+- All paths must exist and be directories
+
+## Setup
+
+First, ensure `uv` is installed (required for all methods below):
+```bash
+which uv || brew install uv
+```
+
+### 1. Claude Code (Recommended)
+
+```bash
+claude mcp add --scope user --transport stdio -- drews-xcode-mcp `which uvx` drews-xcode-mcp
+```
+
+To run a specific version, use:
+```bash
+# Example: How to run v1.3.0b6
+claude mcp add --scope user --transport stdio -- drews-xcode-mcp `which uvx` drews-xcode-mcp==1.3.0b6
+```
+
+That's it! Claude Code handles the rest automatically.
+
+### 2. Claude Desktop
+
+Edit your Claude Desktop config file (`~/Library/Application Support/Claude/claude_desktop_config.json`):
+
+```json
+{
+    "mcpServers": {
+        "drews-xcode-mcp": {
+            "command": "uvx",
+            "args": [
+                "drews-xcode-mcp"
+            ]
+        }
+    }
+}
+```
+
+If you'd like to allow only certain projects or folders to be accessible by drews-xcode-mcp, add the `env` option, with a colon-separated list of absolute folder paths, like this:
+
+```json
+{
+    "mcpServers": {
+        "drews-xcode-mcp": {
+            "command": "uvx",
+            "args": [
+                "drews-xcode-mcp"
+            ],
+            "env": {
+                "XCODEMCP_ALLOWED_FOLDERS": "/Users/andrew/my_project:/Users/andrew/Documents/source"
+            }
+        }
+    }
+}
+```
+
+### 3. Cursor AI
+
+In Cursor: Settings → Tools & Integrations → + New MCP Server
+
+Or edit `~/.cursor/mcp.json` directly:
+
+```json
+{
+    "mcpServers": {
+        "drews-xcode-mcp": {
+            "command": "uvx",
+            "args": ["drews-xcode-mcp"]
+        }
+    }
+}
+```
+
+**Optional:** Add folder restrictions with an `env` section (same format as Claude Desktop above).
+
+## Usage
+
+Once configured, simply ask your AI assistant to help with Xcode tasks:
+
+- "Find all Xcode projects in my home directory"
+- "Build the project at /path/to/MyProject.xcodeproj"
+- "Run tests for this project and show me any failures"
+- "What are the build errors in this project?"
+- "Show me the directory structure of this project"
+- "Take a screenshot of the Xcode window"
+
+Most tools work with paths to `.xcodeproj` or `.xcworkspace` files, or with regular directory paths for browsing and navigation.
+
+## Advanced Configuration
+
+### Command Line Arguments
+
+When running the server directly (for development or custom setups), these options are available:
+
+**Build output control:**
+- `--no-build-warnings` - Show only errors, exclude warnings
+- `--always-include-build-warnings` - Always show warnings (default)
+
+**Notifications:**
+- `--show-notifications` - Enable macOS notifications for operations
+- `--hide-notifications` - Disable notifications (default)
+
+**Access control:**
+- `--allowed /path` - Add allowed folder (can be repeated)
+
+Example:
+```bash
+drews-xcode-mcp --no-build-warnings --show-notifications --allowed ~/Projects
+```
+
+**Note:** When using MCP clients (Claude, Cursor), configure these via the `env` section in your client's config file instead.
+
+## Development
+
+The server is built with FastMCP and uses AppleScript to communicate with Xcode.
+
+### Local Testing
+
+Test with MCP Inspector:
+
+```bash
+export XCODEMCP_ALLOWED_FOLDERS=~/Projects
+mcp dev drews_xcode_mcp/__main__.py
+```
+
+This opens an inspector interface where you can test tools directly. Provide paths as quoted strings: `"/Users/you/Projects/MyApp.xcodeproj"`
+
+## Limitations
+
+- AppleScript syntax may need adjustments for specific Xcode versions
+- Some operations require the project to be open in Xcode first

drews_xcode_mcp-1.3.16b1/drews_xcode_mcp/__init__.py

@@ -0,0 +1,12 @@
+"""Xcode MCP Server - Model Context Protocol server for Xcode integration"""
+
+__version__ = "1.3.16b1"
+
+
+def main():
+    """Entry point that delegates to CLI"""
+    from drews_xcode_mcp.cli import initialize_server
+    return initialize_server()
+
+
+__all__ = ["main", "__version__"]

drews_xcode_mcp-1.3.16b1/drews_xcode_mcp/__main__.py

@@ -0,0 +1,7 @@
+#!/usr/bin/env python3
+"""Xcode MCP Server - Main entry point for python -m"""
+
+from drews_xcode_mcp import main
+
+if __name__ == "__main__":
+    main()

drews_xcode_mcp-1.3.16b1/drews_xcode_mcp/cli.py

@@ -0,0 +1,188 @@
+#!/usr/bin/env python3
+"""Command-line interface and server initialization"""
+
+import os
+import sys
+import subprocess
+import argparse
+import time
+
+from drews_xcode_mcp import __version__
+from drews_xcode_mcp.server import mcp, LEGACY_PACKAGE_NAME
+from drews_xcode_mcp.security import get_allowed_folders, set_allowed_folders
+from drews_xcode_mcp.utils.applescript import set_notifications_enabled, show_notification
+from drews_xcode_mcp.utils.xcresult import set_build_warnings_enabled, freeze_build_warnings_settings
+
+_LEGACY_RENAME_NOTIFICATION_INTERVAL_SECONDS = 24 * 60 * 60
+
+
+def _show_legacy_rename_notification_if_needed():
+    """Show a macOS notification about the package rename, at most once a day.
+
+    This pop-up is the migration channel the user sees directly; the LLM-facing
+    channels (server instructions, version tool, migration prompt) live in
+    server.py. Throttled via a marker file because MCP clients start a fresh
+    server process per session, which could otherwise nag on every restart.
+    """
+    if not LEGACY_PACKAGE_NAME:
+        return
+
+    # Constructing the ConfigManager first lets it migrate ~/.xcode-mcp-server
+    # to ~/.drews-xcode-mcp; touching the marker path directly here would create
+    # the new directory prematurely and strand the old settings.
+    from drews_xcode_mcp.config_manager import ConfigManager
+    try:
+        marker = ConfigManager()._config_dir / "legacy-rename-notified"
+        if marker.exists() and time.time() - marker.stat().st_mtime < _LEGACY_RENAME_NOTIFICATION_INTERVAL_SECONDS:
+            return
+        marker.parent.mkdir(parents=True, exist_ok=True)
+        marker.touch()
+    except OSError:
+        # A notification is never worth failing startup over.
+        return
+
+    show_notification(
+        "Xcode MCP Server renamed",
+        subtitle=f"'{LEGACY_PACKAGE_NAME}' is now 'drews-xcode-mcp'",
+        message="Your current setup still works. When convenient, update your MCP config to run 'drews-xcode-mcp'.",
+    )
+
+
+def initialize_server():
+    """Entry point for the drews-xcode-mcp command"""
+    # Debug
+    print(f"Drew's Xcode MCP Server (drews-xcode-mcp) v{__version__}", file=sys.stderr)
+
+    # Parse command line arguments
+    parser = argparse.ArgumentParser(description="Drew's Xcode MCP Server")
+    parser.add_argument("--version", action="version", version=f"drews-xcode-mcp {__version__}")
+    parser.add_argument("--configure", action="store_true", help="Launch configuration UI")
+    parser.add_argument("--allowed", action="append", help="Add an allowed folder path (can be used multiple times)")
+    parser.add_argument("--show-notifications", action="store_true", help="Enable notifications for tool invocations")
+    parser.add_argument("--hide-notifications", action="store_true", help="Disable notifications for tool invocations")
+    parser.add_argument("--no-build-warnings", action="store_true", help="Exclude warnings from build output")
+    parser.add_argument("--always-include-build-warnings", action="store_true", help="Always include warnings in build output")
+    args = parser.parse_args()
+
+    # Handle --configure flag
+    if args.configure:
+        from drews_xcode_mcp.config_ui import run_configuration_ui
+        run_configuration_ui()
+        sys.exit(0)
+
+    # Handle notification settings
+    if args.show_notifications and args.hide_notifications:
+        print("Error: Cannot use both --show-notifications and --hide-notifications", file=sys.stderr)
+        sys.exit(1)
+    elif args.show_notifications:
+        set_notifications_enabled(True)
+        print("Notifications enabled", file=sys.stderr)
+    elif args.hide_notifications:
+        set_notifications_enabled(False)
+        print("Notifications disabled", file=sys.stderr)
+
+    # Handle build warning settings
+    if args.no_build_warnings and args.always_include_build_warnings:
+        print("Error: Cannot use both --no-build-warnings and --always-include-build-warnings", file=sys.stderr)
+        sys.exit(1)
+    elif args.no_build_warnings:
+        set_build_warnings_enabled(False, forced=True)
+        print("Build warnings forcibly disabled", file=sys.stderr)
+    elif args.always_include_build_warnings:
+        set_build_warnings_enabled(True, forced=True)
+        print("Build warnings forcibly enabled", file=sys.stderr)
+
+    # Construct the ConfigManager up front so the one-time migration of
+    # ~/.xcode-mcp-server to ~/.drews-xcode-mcp happens at startup, where its
+    # stderr note lands in the launch log, rather than lazily inside the first
+    # tool call. This also protects any future startup code that touches the
+    # config directory from stranding the legacy settings.
+    from drews_xcode_mcp.config_manager import ConfigManager
+    try:
+        ConfigManager()
+    except OSError as e:
+        # An unusable config directory is not worth failing startup over;
+        # before this eager construction the same failure surfaced at the
+        # first tool call, and it still will (the singleton is only cached
+        # on successful construction).
+        print(f"Warning: could not initialize config directory: {e}", file=sys.stderr)
+
+    # After notification settings are applied, so --hide-notifications is honored
+    _show_legacy_rename_notification_if_needed()
+
+    # Initialize allowed folders from environment and command line
+    allowed_folders = get_allowed_folders(args.allowed)
+    set_allowed_folders(allowed_folders)
+
+    # Check if we have any allowed folders
+    if not allowed_folders:
+        error_msg = """
+========================================================================
+ERROR: Xcode MCP Server cannot start - No valid allowed folders!
+========================================================================
+
+No valid folders were found to allow access to.
+
+To fix this, you can either:
+
+1. Set the XCODEMCP_ALLOWED_FOLDERS environment variable:
+   export XCODEMCP_ALLOWED_FOLDERS="/path/to/folder1:/path/to/folder2"
+
+2. Use the --allowed command line option:
+   drews-xcode-mcp --allowed /path/to/folder1 --allowed /path/to/folder2
+
+3. Ensure your $HOME directory exists and is accessible
+
+All specified folders must:
+- Be absolute paths
+- Exist on the filesystem
+- Be directories (not files)
+- Not contain '..' components
+
+========================================================================
+"""
+        print(error_msg, file=sys.stderr)
+
+        # Show macOS notification
+        try:
+            subprocess.run(['osascript', '-e',
+                          'display alert "Drew\'s Xcode MCP Server Error" message "No valid allowed folders found. Check your configuration."'],
+                          capture_output=True)
+        except Exception:
+            pass
+
+        sys.exit(1)
+
+    # Debug info
+    print(f"Total allowed folders: {allowed_folders}", file=sys.stderr)
+    cwd = os.getcwd()
+    print(f"Working directory: {cwd}", file=sys.stderr)
+
+    # Import all tools to register them with the MCP server
+    # This must be done before mcp.run()
+    from drews_xcode_mcp import tools
+
+    # Show startup notification
+    from drews_xcode_mcp.utils.applescript import show_notification
+
+    # Format the working directory relative to home if possible
+    home = os.path.expanduser("~")
+    if cwd.startswith(home):
+        # Make it relative to home with ~ prefix
+        display_cwd = "~" + cwd[len(home):]
+    else:
+        display_cwd = cwd
+
+    show_notification(
+        f"Drew's Xcode MCP Server - v{__version__}",
+
+        message="Working dir: " + display_cwd,
+        subtitle="✅ Server started"
+    )
+
+    # Lock startup-only globals so any later mutation surfaces as a
+    # RuntimeError instead of silently racing concurrent tool readers.
+    freeze_build_warnings_settings()
+
+    # Run the server
+    mcp.run()