Codex Setup
Codex is a coding agent that runs in your terminal. Once you connect the WEEGLOO MCP server to it, Codex can directly create, read, and modify resources such as Content Type, Content, and Media. Along with the MCP server, the install tool also installs Skills and Rules so that Codex uses the WEEGLOO API the way it is meant to be used. Skills are guides that capture how to do a specific task well, and Rules are rules to follow across all tasks. You set everything up at once with the install tool, then complete MCP-connection authentication.
For details on the MCP server and on Skills and Rules, see the MCP and Skills and Rules pages respectively. This page covers only how to connect to Codex.
Prerequisites
Running the install commands below requires Node.js. First, use the following commands to check whether it is installed and whether the version is 18 or higher.
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.
If winget is missing or not recognized, download the LTS installer from nodejs.org. After installing, you need to open a new terminal.
Distribution packages can be outdated, so we recommend installing with nvm, which works across many distributions.
To download the installer directly, check nodejs.org.
Codex must also be installed so that you can run it from your terminal with the codex command. If you do not have it yet, see the Codex CLI install guide.
Connecting
For a default install, copy the install command on this page and run it once in your terminal. To go through the install steps and choose each one yourself, open Custom install.
Install MCP and Skills
Copy the install command and run it in your terminal.
Authenticate the MCP connection
Authenticate in the following order.
-
Running the command below in your terminal opens the WEEGLOO authentication page in your browser.
Terminalcodex mcp login weegloo -
On the WEEGLOO authentication page that opens, copy your token with the Copy token button below, paste it, and click Connect Server. An agent that was already running needs to be restarted after authentication completes for the changes to take effect.

Install MCP and 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 the MCP connection
Authenticate in the following order.
-
Running the command below in your terminal opens the WEEGLOO authentication page in your browser.
Terminalcodex mcp login weegloo -
On the WEEGLOO authentication page that opens, copy your token with the Copy token button below, paste it, and click Connect Server. An agent that was already running needs to be restarted after authentication completes for the changes to take effect.

Run npx weegloo interactively and install by choosing the prompted items yourself.
Run the install tool
Run the command below in your terminal and choose each prompted item in turn. Where it asks for the token, use the Copy token button below to copy the token and paste it.
Authenticate the MCP connection
Authenticate in the following order.
-
Running the command below in your terminal opens the WEEGLOO authentication page in your browser.
Terminalcodex mcp login weegloo -
On the WEEGLOO authentication page that opens, copy your token with the Copy token button below, paste it, and click Connect Server. An agent that was already running needs to be restarted after authentication completes for the changes to take effect.

Run the install tool
Move to the project folder you want to connect, then run the command below in that folder and choose each prompted item in turn. Where it asks for the token, use the Copy token button below to copy the token and paste it. Be sure to run it inside that project folder.
Authenticate the MCP connection
Authenticate in the following order.
-
Running the command below in your terminal opens the WEEGLOO authentication page in your browser.
Terminalcodex mcp login weegloo -
On the WEEGLOO authentication page that opens, copy your token with the Copy token button below, paste it, and click Connect Server. An agent that was already running needs to be restarted after authentication completes for the changes to take effect.

MCP Server Configuration File
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 weegloo server connects to https://ai.weegloo.com/mcp over HTTP, while the weegloo-upload server, which handles files, runs via npx and uses a Personal Access Token for authentication. With a Global install it is registered at ~/.codex/config.toml in your home directory, and with a Project install at .codex/config.toml inside the project folder.
[mcp_servers.weegloo]
url = "https://ai.weegloo.com/mcp"
[mcp_servers.weegloo-upload]
command = "npx"
args = ["-y", "weegloo-upload"]
[mcp_servers.weegloo-upload.env]
UPLOAD_API_URL = "https://upload.weegloo.com/v1"
AUTH_BEARER_TOKEN = "<Personal Access Token>"To change the server group, append a group value to the end of the weegloo server's url. For example, to use all tools, write it as https://ai.weegloo.com/mcp?group=all. For the tool composition of each group, refer to MCP Server Groups.
With a Project install, the install tool also adds one entry to ~/.codex/config.toml in your home directory. Codex reads the .codex/config.toml inside a folder only for projects it trusts. Without this entry, the MCP server you just registered is ignored, so the install tool marks that project as trusted. The path slot holds the actual path of the project folder where you ran the install.
[projects."/Users/jimin/projects/jeju-shop"]
trust_level = "trusted"Skills
The install tool places each Skill as a single directory under .agents/skills/. A global install uses ~/.agents/skills/, and a project install uses .agents/skills/ in the project folder; Codex reads Skills from this location.
Rules
Codex has no separate concept of Rules. So the install tool puts the content that corresponds to Rules, that is, content that plays the same role as Claude Code's Rules, into the AGENTS.md file. A global install uses ~/.codex/AGENTS.md, and a project install uses the AGENTS.md in the project folder.
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.
- Keeping up to date: Covers how to keep the Skills and Rules you installed up to date.
- 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.
