Codex setup guide

Give Codex revenue context.

Codex desktop, CLI, and IDE share MCP configuration on the same host. Add the VerifiedMRR endpoint once, authenticate, and use read-only revenue tools while planning launches, reviewing projects, or writing reports.

Open free dashboard See pricing

Add it in Codex

Open Settings → MCP servers, choose Add server, select Streamable HTTP, and enter https://verifiedmrr.com/mcp. Save, restart the client when prompted, and choose Authenticate to complete OAuth.

In the Codex terminal UI, /mcp shows the connected server and its tools. The same host configuration is shared by the desktop app, CLI, and IDE extension.

Configure OAuth in config.toml

For a durable configuration, add this table to ~/.codex/config.toml. OAuth is the default authentication mode for remote HTTP servers; run codex mcp login verifiedmrr to authorize.

[mcp_servers.verifiedmrr]
url = "https://verifiedmrr.com/mcp"
auth = "oauth"
enabled = true
required = false
default_tools_approval_mode = "writes"

Use an environment-backed bearer token

For CI or a headless Codex host, create a VerifiedMRR personal MCP token and keep it in an environment secret. bearer_token_env_var names the variable; it does not put the token itself in config.toml.

[mcp_servers.verifiedmrr]
url = "https://verifiedmrr.com/mcp"
bearer_token_env_var = "VERIFIEDMRR_MCP_TOKEN"
enabled = true

Paste this after setup

Use this in a fresh Codex thread after the MCP server is authenticated.

Verify my VerifiedMRR MCP connection in Codex. List the available VerifiedMRR tools, call get_sync_status, then call list_projects. Report whether authentication works, whether any source is stale or degraded, and which read-only analyses are now available. Do not combine currencies or expose credentials.

Keep exploring

Keep configuring.

MCP overviewSee the complete server surface.Connect ChatGPTUse a custom app or Responses API.Codex MCP documentationOfficial desktop, CLI, IDE, OAuth, and config reference.

FAQ

Before you connect a provider.

Where does Codex store MCP configuration?

The default is ~/.codex/config.toml. A trusted project can also use .codex/config.toml for project-scoped configuration.

Do I need to paste a token into config.toml?

No. Use OAuth interactively, or set bearer_token_env_var to the name of an environment variable that contains your personal MCP token.

Which Codex clients can use the server?

The Codex desktop app, CLI, and IDE extension support Streamable HTTP MCP servers and share configuration for the same Codex host.

Let Codex see the business context.

Connect read-only revenue data alongside the code and tools Codex already uses.

Open free dashboard