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. The connection works the same way as in other environments. You set everything up at once with the install tool, then just complete authentication in Codex.

MCP itself, the server groups, and the file upload server are covered in MCP. This page covers only the steps to connect to Codex.

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.

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

Choose the install location, then follow the guide below. To connect only a single project, choose Project; to use it across all projects, choose Global.

GlobalProject

1

Install MCP · Skills

Copy the install command and run it in your terminal.

Terminal

$ npx weegloo@latest -y \ --agent codex \ --token wgl_••••••••••••

Copy command

2

Authenticate MCP

Authenticate in the order below.

1. 1.Run the command below in your terminal — it opens a WEEGLOO authentication page in your browser.
   Terminal

   codex mcp login weegloo
2. 2.On the WEEGLOO authentication page that opens, copy your token with the Copy token button below, paste it, and click Connect server. After authenticating, restart the agent if it was already running.

Copy token

Inspecting the Configuration File Yourself

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 servers you just registered are 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"

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.