Choose the connection you need

Codex supports local servers launched over stdio and remote servers reached through Streamable HTTP. A local server needs its executable and runtime available; a remote server needs a reachable endpoint and the required authentication.

Use the server listing's original installation guide. A generic MCP badge does not tell you which transport, credentials or tool permissions are required.

A documented local example

OpenAI's MCP documentation provides the following Context7 example. It registers a local command that launches the package through npx. Review the provider's runtime requirements and authentication options before using it.

This example does not configure a Context7 API key. For the provider's remote configuration or higher-limit authentication, follow its client guide.

codex mcp add context7 -- npx -y @upstash/context7-mcp
Review before running

Remote servers and authentication

Remote setup is provider-specific. Figma documents a Codex command followed by authentication. GitHub's hosted Codex guide uses a PAT supplied through an environment variable.

Keep credentials out of source files and shared install examples. Do not copy a configuration from another client without checking the provider's Codex guide, because authentication support can differ.

Scope and verify your connection

Codex normally stores MCP configuration in ~/.codex/config.toml. A trusted project can use .codex/config.toml for project-scoped configuration. Local Codex clients on the same host share their configuration.

Inspect the configured server list, complete any outstanding login, and start with a small task against a known resource. Confirm access and output before relying on the connection for broader work.

codex mcp list
Review before running

Source documentation

Find your next capabilityBrowse the source-linked Codex directory.