How to connect Re:amaze to Codex

  • Codex gets 35 Re:amaze tools through one Metorial MCP URL.
  • Setup is 3 steps; teammates then sign in with SSO.
  • You need the Codex CLI, IDE extension or ChatGPT desktop app.

What Codex can do with Re:amaze

Ask your agent in plain language. Each of these maps to a real tool on the server.

  • Ask Codex to use the get conversation tool in Re:amaze
  • Ask Codex to use the update contact tool in Re:amaze
  • Ask Codex to use the delete contact note tool in Re:amaze
  • Ask Codex to use the list systems tool in Re:amaze
  • Ask Codex to use the list incidents tool in Re:amaze

Add the Re:amaze MCP server to Codex

Run these once. Afterwards, everyone you give access to signs in the same way.

  1. 1. Enable Re:amaze in Metorial

    In your Metorial portal, enable the Re:amaze MCP server and sign in with the account that owns the data. Access stays governed by your team policies.

  2. 2. Add the server and sign in

    The Codex CLI, IDE extension and ChatGPT desktop app share this config.

    codex mcp add metorial --url <your-magic-mcp-url>
    codex mcp login metorial
  3. 3. Check the connection

    Type /mcp in Codex to see Metorial and its Re:amaze tools.

Give your team Re:amaze in Codex

Once Re:amaze is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Re:amaze tools available in Codex

Full descriptions and inputs are on the Re:amaze MCP server page.

  • List Contact Notes: Retrieve all notes attached to a specific contact, including their canonical noteIdentifier values for updates and deletion.
  • Create Conversation: Create a new support conversation with a subject, message body, customer info, and channel assignment.
  • Update Conversation: Update an existing conversation's status, assignee, tags, channel, or custom fields.
  • Create Staff Member: Create a new staff user account in your Re:amaze account.
  • Create Article: Create a new knowledge base / FAQ article.
  • List Satisfaction Ratings: Retrieve customer satisfaction ratings.
  • List Response Templates: List and search pre-written response templates.
  • List Articles: List and search knowledge base articles.
  • Create Incident: Create a new status page incident with a title, initial status update, and optionally associate affected systems with their operational status.
  • List Conversations: List and filter support conversations.
  • Update Response Template: Update an existing response template's name, body content, or personal/shared setting.
  • Create Contact: Create a new customer contact record with a name and either an email address or mobile phone number (E.164 format).
  • Create Response Template: Create a new pre-written response template for staff to use when replying to conversations.
  • List Contacts: Search and list customer contacts across the account.
  • Update Article: Update an existing knowledge base article's title, body, status, or topic assignment.
  • And 20 more on the Re:amaze MCP server page.

Using Re:amaze tools in Codex

What to expect once Re:amaze is connected.

  • Limit which Re:amaze tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
  • Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
  • Type /mcp in the composer to see the connected servers.
  • Override the approval behavior for a single Re:amaze tool with tools.<tool>.approval_mode.

Troubleshooting Codex

Metorial is listed but tools are missing
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.
Metorial times out at startup
Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.
Long tool calls fail after a minute
The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.

Frequently asked questions

Common questions about connecting Re:amaze to AI agents with Metorial.

  1. Does Codex support the Re:amaze MCP server?
    Yes. Codex connects to the Re:amaze MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
  2. No. You sign in to Re:amaze once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
  3. All 35 Re:amaze tools your team allows, such as List Contact Notes, Create Conversation, Update Conversation. Admins can narrow that list per team.
  4. Yes. Role-based access control decides who can use Re:amaze and which of its tools appear in Codex, and every call is logged with the person's identity.
  5. Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.