Move your MCP servers

MCP servers are one part of your setup you re-enter in Gloo Code. They go in the mcp section of gloocode.json, and each conversion takes a minute or two.

Where the config lives

Scope	File
Just this project	`gloocode.json` at the project root
All your projects	`~/.config/gloocode/gloocode.json`

Both files allow comments. Servers in a project’s gloocode.json apply after you trust the folder, and after you trust the folder, Gloo Code asks you to approve each server the project defines. If a server’s command or URL changes, it asks again. Type /mcps inside Gloo Code to see your servers.

The format

Each server is an entry under mcp, named by its key. There are two types.

Local (runs on your machine)
Remote (over HTTP)

gloocode.json

{
  "mcp": {
    "fs": {
      "type": "local",
      "command": ["npx", "-y", "@modelcontextprotocol/server-filesystem", "/repo"],
      "environment": { "LOG_LEVEL": "info" },
      "enabled": true,
      "timeout": 30000
    }
  }
}

command is a single array that holds the program and all of its arguments.
environment holds environment variables for the process.

gloocode.json

{
  "mcp": {
    "api": {
      "type": "remote",
      "url": "https://api.example.com/mcp",
      "headers": { "Authorization": "Bearer {env:API_KEY}" },
      "enabled": true,
      "timeout": 30000
    }
  }
}

url is the server’s address. Gloo Code connects over Streamable HTTP and falls back to SSE.
headers are sent with each request.

Other keys:

enabled: set to false to keep a server in the file without loading it.
timeout: milliseconds allowed for connecting, listing tools, and each tool call.
oauth: for remote servers that sign in with OAuth, run gloocode mcp auth <name> and follow the browser prompt. gloocode mcp auth list shows what is signed in.

Keep secrets out of the file

Write {env:NAME} anywhere in the config and Gloo Code fills it from your shell environment. Use {file:path} to read a value from a file.

gloocode.json

{
  "mcp": {
    "api": {
      "type": "remote",
      "url": "https://api.example.com/mcp",
      "headers": { "Authorization": "Bearer {env:API_KEY}" }
    }
  }
}

Add a server with the wizard

Prefer prompts to editing JSON? Run gloocode mcp add. It asks whether the server is for this project or all projects, what to name it, whether it is local or remote, and whether it uses OAuth. gloocode mcp list shows what you have.

Notion and Linear are built into Gloo Code as connectors, so give a server of your own a different name than notion or linear.

From Claude Code

A Claude Code .mcp.json uses mcpServers. In gloocode.json the key is mcp, a local server’s command and args merge into one array, env becomes environment, and ${VAR} becomes {env:VAR}.

{
  "mcpServers": {
    "fs": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/repo"],
      "env": { "X": "${X}" }
    },
    "api": {
      "type": "http",
      "url": "https://api.example.com/mcp",
      "headers": { "Authorization": "Bearer ${API_KEY}" }
    }
  }
}

{
  "mcp": {
    "fs": {
      "type": "local",
      "command": ["npx", "-y", "@modelcontextprotocol/server-filesystem", "/repo"],
      "environment": { "X": "{env:X}" }
    },
    "api": {
      "type": "remote",
      "url": "https://api.example.com/mcp",
      "headers": { "Authorization": "Bearer {env:API_KEY}" }
    }
  }
}

`.mcp.json`	`gloocode.json`
`mcpServers`	`mcp`
`command` plus `args`	`"type": "local"` and one `command` array
`env`	`environment`
`"type": "http"` or `"sse"`, `url`	`"type": "remote"`, `url`
`${VAR}`	`{env:VAR}`
`headers`	`headers`

From Codex

In Codex each server is a [mcp_servers.<name>] table. Convert it to an entry under mcp.

[mcp_servers.docs]
command = "npx"
args = ["-y", "some-mcp"]
env = { TOKEN = "x" }
startup_timeout_sec = 20

{
  "mcp": {
    "docs": {
      "type": "local",
      "command": ["npx", "-y", "some-mcp"],
      "environment": { "TOKEN": "x" },
      "timeout": 20000
    }
  }
}

`config.toml`	`gloocode.json`
`[mcp_servers.<name>]`	`mcp` entry named `<name>`
`command` plus `args`	`"type": "local"` and one `command` array
`env`	`environment`
`url`	`"type": "remote"`, `url`
`bearer_token_env_var = "T"`	`"headers": { "Authorization": "Bearer {env:T}" }`
`startup_timeout_sec = 20`	`"timeout": 20000` (milliseconds; also limits each tool call, so raise it if tools run long)

To keep a secret out of the file, export it and use {env:TOKEN}.

Check that it worked

Export your secrets

Set any variables you referenced with {env:...} in your shell before starting Gloo Code.

Start Gloo Code and trust the folder

Run gloocode in the project. Approve the folder and any project MCP server when asked.

List your servers

Type /mcps in a session, or run gloocode mcp list in a terminal.

Try a tool

Ask the agent to do something your server enables, such as “List the files the filesystem server can see”.

Next steps

Migration checklist

A copy-and-paste checklist for your first day.

From Claude Code

Skills, commands, and day-to-day shortcuts.

From Codex CLI

AGENTS.md and day-to-day equivalents.

Ask Gloo Code

Ask Gloo Code about any config key.

Start Here

Inference and APIs

Data Engine

Studio

Gloo Code

Learn More

Legacy

Move your MCP servers

Where the config lives

The format

Keep secrets out of the file

Add a server with the wizard

From Claude Code

From Codex

Check that it worked

Next steps

Migration checklist

From Claude Code

From Codex CLI

Ask Gloo Code

​Where the config lives

​The format

​Keep secrets out of the file

​Add a server with the wizard

​From Claude Code

​From Codex

​Check that it worked

​Next steps

Migration checklist

From Claude Code

From Codex CLI

Ask Gloo Code

Where the config lives

The format

Keep secrets out of the file

Add a server with the wizard

From Claude Code

From Codex

Check that it worked

Next steps