Codex MCP servers and connections for external tools
Explore Model Context Protocol connections that let Codex work with external services and data. Each entry separates the endpoint, parent plugin and canonical source so configuration can be verified before use.
What MCP adds to a Codex workflow
Skills provide instructions; MCP connections provide access. An MCP server can expose tools or structured data from an external service, making it useful when the agent needs to inspect, query or act on systems beyond the local conversation or codebase.
Check authentication and scope first
Before connecting an MCP server, review the endpoint, authentication model and the permissions required by the service. The fact that an integration exists does not mean every workflow needs the same level of account access.
MCP and plugins often work together
Many MCP connections are delivered through a parent plugin. Artifiner records that relationship so you can understand whether the endpoint is installed independently or enabled as part of a larger plugin package.
Browse Codex MCP integrations by tool and use case
Search the source-backed catalog, refine by category or provenance, and open an entity page for installation, compatibility and upstream verification.