Skip to main content
This page covers where org-level control over Pleo MCP access actually lives for Codex, since Codex CLI has no admin console of its own. Codex CLI reads its MCP server configuration from a file on each developer’s own machine (~/.codex/config.toml), so there’s no “add a custom connector” step for an admin to complete here. Instead, control over custom connectors sits in one of the following places, depending on how your organisation runs Codex:
  • Using Codex through a ChatGPT Business, Enterprise, or Edu workspace: your workspace admin controls custom connectors centrally. See How to Add Pleo MCP as a Custom Connector in ChatGPT.
  • Using Codex CLI directly on developer machines: there’s no product-level restriction. If your organisation needs to restrict outbound connections, this is a network-level control (for example, allowlisting mcp.pleo.io at the firewall or proxy) managed by your IT or security team, not a Codex setting.
Once your organisation’s network and Pleo-side access allow it, individual developers can connect Codex to Pleo themselves. See How to Install the Pleo MCP in Codex.

​
What Comes Next?