Skip to main content
This page covers native MCP in Codex. The remote service uses Streamable HTTP and browser OAuth without requiring EvoLink CLI. For command and skill execution, use the separate CLI guide.

​
Connect remote MCP

For native tools, use Streamable HTTP + OAuth with this server URL:
CLI installation is not required. Back up existing configuration, merge only EvoLink, and preserve other services. Choose command-based or manual registration.
1

Add the remote server

In a terminal with Codex CLI installed, run:
The configuration should contain evolink. Inspect an existing entry before adding; avoid duplicate manual and plugin registrations.
2

Authorize MCP separately

Sign in to EvoLink in the browser, approve, and wait for completion. Skip a repeated login if adding already completed authorization. evolink auth login does not authorize this native connection.
3

Check the connection and query balance

Open a new Codex session or use /mcp, then send the free verification prompt below. Success means actual account balance and available models are returned.
For manual configuration, merge only this section into user ~/.codex/config.toml or a trusted project’s .codex/config.toml:
Codex App has its own plugin/custom MCP connection with the same URL and OAuth. Signing in to the terminal CLI does not automatically connect the App. See Codex documentation. After authorization, send this in the agent chat:
Success: actual check_balance and search_models calls return results. Verify these tools in the actual MCP connection.

​
Updates, disconnection, and troubleshooting

EvoLink updates the hosted MCP server. Refresh the actual client session after configuration changes. Reauthorize through that client’s OAuth action when needed. Disable, sign out, or remove EvoLink in host MCP settings to disconnect; retain other servers. See MCP costs, access, and troubleshooting. Read the creation workflow before submitting; call shapes are in the MCP tool reference.