Codex Setup

Last updated: June 22, 2026

This page covers how to connect the WEEGLOO MCP server in Codex. Once connected, Codex can directly query, create, and modify WEEGLOO resources. The full flow, server groups, and the file upload server are covered in MCP. This page describes only the connection steps specific to Codex.

Prerequisites

Before connecting, you need the following.

  • Codex: Codex must be installed.
  • Node.js 18 or higher: Required to run the installer and the file transfer server (weegloo-upload). You can get it from Node.js download.
  • Personal Access Token: Used for authentication. A Personal Access Token is the key an account uses to call APIs with its own permissions. How to issue one is covered in Issuing a Personal Access Token.

Connecting with the installer

When you use the installer, the MCP server is registered automatically in the Codex configuration file. Run the following in your project folder.

npx weegloo@latest

When you run it, it asks a series of questions. Here is what each question means.

  1. Select plugin version (branch): Choose the version of Skills and Rules. Usually you choose latest.
  2. Select your IDE: Choose Codex.
  3. What would you like to install?: You can install the MCP server and Skills / Rules separately. If this is your first install, install everything.
  4. Enter your Weegloo Personal Access Token: Enter the Personal Access Token you issued earlier.
  5. Select the MCP server group: For general use, choose default. The kinds of server groups are covered in MCP.
  6. Where would you like to install Codex configuration: Choose Project to apply it only to the current project, or Global to apply it to all projects. Depending on your Codex version, Project installation may not be supported, in which case you install with Global.

When the installation finishes, the setup tool registers the MCP server in the Codex configuration file (config.toml). A Global install registers it in ~/.codex/config.toml, and a Project install registers it in the project's Codex configuration file.

Logging in to the MCP server

The weegloo server connects over HTTP, and you need to log in once separately from the installation. The installer runs this login step next. If it does not run automatically, run the following yourself.

codex mcp login weegloo

When you run it, an authentication page opens in your browser. Once you finish authentication, the weegloo server connection is complete. The file transfer server weegloo-upload authenticates with the Personal Access Token placed in the configuration file, so it does not need this login step.

Editing the configuration file directly

Instead of the installer, you can edit the Codex configuration file (config.toml) directly. The weegloo server connects over HTTP.

[mcp_servers.weegloo]
url = "https://ai.weegloo.com/mcp"

To specify a server group, append a group value to the end of the address. For example, to use all tools, write it as follows.

[mcp_servers.weegloo]
url = "https://ai.weegloo.com/mcp?group=all"

The file transfer server weegloo-upload runs as a command and uses a Personal Access Token for authentication. In the token slot, put the Personal Access Token you issued.

[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>"

If you edited the configuration file directly, restart Codex. After that, log in to the weegloo server once with the Logging in to the MCP server step above.

What to do next

  • MCP: Covers the full picture of the connection, including server groups and the file upload server.
  • Skills and Rules: Covers the Skills and Rules that the installer can install alongside.
  • Migrate static pages with AI: Follow the flow of moving a real page into a content-based service with the connected MCP.