Skip to main content
Codex starts stdio MCP servers, and supports MoleSignal’s Streamable HTTP endpoint and OAuth discovery. The client starts the MoleSignal CLI, which carries the messages to MoleSignal. It needs Node.js 20 or later.
1

Sign in once

The browser opens on MoleSignal to approve the sign-in; the CLI keeps it and renews it.
2

Add MoleSignal

Or in ~/.codex/config.toml:
Where no browser is at hand, set MOLESIGNAL_URL and MOLESIGNAL_TOKEN (an API token) in the server’s environment instead of signing in. See Connect over stdio. The sections below connect over Streamable HTTP, without the CLI.

​
Connect with OAuth 2.1

1

Register MoleSignal

2

Authorize the connection

Complete the MoleSignal authorization page in the browser.
3

Verify the server

Restart the active Codex task or open a new task so the MCP tool list is refreshed.
Do not add --oauth-resource. MoleSignal already publishes the protected resource through OAuth discovery. Adding the same value again can produce duplicate field resource.

​
Connect with an API token

Use a personal or Service Account API token for a non-interactive Codex process:
Codex stores the environment-variable name rather than the token value. Make the variable available to the process that launches Codex.

​
Verify tool discovery

Ask Codex:
Use the MoleSignal MCP server. Search for incident tools and list active incidents. Do not make changes.
The first request should use tool_search, then call_read_tool for a deferred read. See the official Codex MCP documentation.
Last modified on October 18, 2026