Xcode Setup
Last updated: July 10, 2026
Xcode can run coding agents such as Claude Code and Codex inside its own interface. Once you connect the WEEGLOO MCP server to it, the agent running inside Xcode can directly create, read, and modify resources such as Content Type, Content, and Media. Below, choose the agent you want to use inside Xcode, set everything up at once with the install tool, then just complete authentication.
MCP itself, the server groups, and the file upload server are covered in MCP. This page covers only the steps to connect to Xcode.
Prerequisites
Running the install commands below requires Node.js. First, check whether it is installed and whether the version is 18 or higher with the following commands.
If Node.js is installed but npx is not, update npm to the latest version with the command below. Updating npm installs npx along with it.
If Node.js is not installed or its version is too old, install Node.js using the method that fits your operating system.
If you do not have Homebrew, install it first from brew.sh, or download Node.js directly from nodejs.org.
Xcode must also be installed. If you do not have it yet, you can get it from Download Xcode.
Connecting
Choose the agent you want to use inside Xcode, then follow the guide below. An Xcode connection is always installed into the current project, so run the install command inside the project folder you want to connect.
Install MCP · Skills
Copy the install command and run it in your terminal. Be sure to run it inside the project folder you want to connect.
Authenticate MCP
Authenticate in the order below.
- 1.Run Claude Code in your terminal. Be sure to run it inside the project folder you want to connect.Terminalclaude
- 2.On first run, Claude Code may ask which new MCP servers to enable. If it does, make sure
weeglooandweegloo-uploadare checked and pressEnterto submit.TerminalNew MCP servers found in .mcp.json Select any you wish to enable. > [√] weegloo [√] weegloo-upload - 3.Type
/mcpto open the MCP server management screen.Terminal/mcp - 4.Select
weeglooin the list. It shows asneeds authentication.TerminalManage MCP servers > weegloo · ∆ needs authentication weegloo-upload · √ connectedIf the servers are not in the list
Ifweeglooandweegloo-uploadare not in the list, you may not have submitted them on the enable screen in step 2, or they are disabled. Quit Claude Code, run the command below in your terminal, then runclaudeagain. When the same screen as step 2 appears, make sureweeglooandweegloo-uploadare checked and pressEnterto submit.Terminalclaude mcp reset-project-choices - 5.Confirm the URL is
https://ai.weegloo.com/mcpand chooseAuthenticate.TerminalWeegloo MCP Server Status: ∆ needs authentication URL: https://ai.weegloo.com/mcp > 1. Authenticate 2. Disable - 6.Choosing
Authenticateopens a WEEGLOO authentication page like the one below in your browser. Copy your token with the Copy token button, paste it, and click Connect server. Whenweeglooturnsconnected, you are done.

Inspecting the Configuration File Yourself
The install tool automatically creates and manages the configuration file, so you do not need to check it yourself. The content below is reference material for users who need the concrete configuration file structure and paths.
The install tool registers the server in the configuration file of the agent you chose to use inside Xcode. An Xcode connection is always installed into the current project, so the file is created inside the project folder too. The file differs depending on the agent you chose.
- Claude Code:
.mcp.jsonin the project folder (the format is the same as in Claude Code Setup) - Codex:
.codex/config.tomlin the project folder (the format is the same as in Codex Setup)
There is one difference specific to using it inside Xcode. A PATH entry is added to the env of the weegloo-upload server, which handles files. Xcode runs agents with a minimal PATH, and without this entry it cannot find the npx needed to run the server. For Claude Code (.mcp.json), it looks like the following.
{
"mcpServers": {
"weegloo-upload": {
"command": "npx",
"args": ["-y", "weegloo-upload"],
"env": {
"PATH": "/Users/jiwoo/.nvm/versions/node/v22.14.0/bin:/usr/bin:/bin",
"UPLOAD_API_URL": "https://upload.weegloo.com/v1",
"AUTH_BEARER_TOKEN": "<Personal Access Token>"
}
}
}
}This PATH is hardcoded with the location of the Node that ran the install. If you move Node to a new version, this path no longer matches, so after upgrading, run the install tool again to refresh the value.
What to Do Next
- MCP: Covers the foundations of the connection, such as server groups and the file upload server.
- Skills and Rules: Covers what the Skills and Rules that the install tool sets up alongside it are.
- Migrating Static Pages with AI: Follow the flow of migrating a real page into a content-based service with the MCP connection you set up.
