Connect Notion (MCP token) to Codex
Notion's hosted MCP server, reached with a token instead of a browser sign-in, so agents can connect with nobody there to approve it. Needs a Business or Enterprise plan.
MCP serverOfficialChecked 2026-11-16
Before you start
- Codex installed (see its MCP documentation (opens in a new tab)).
- Notion (MCP token) is available on macOS, Windows, Linux and the web.
- Only workspace owners on Business and Enterprise plans can create a token, with New MCP token in Notion's Developer portal. Set it as
NOTION_MCP_TOKENin your environment. On other plans, use the Notion entry, which signs in through your browser.
Step 1: Add Notion (MCP token) to Codex
Add it from the terminal
Saves the server to
~/.codex/config.toml, so it works in every project.Terminal codex mcp add notion-token --url https://mcp.notion.com/mcp --bearer-token-env-var NOTION_MCP_TOKENOr edit the config file
Add this to
~/.codex/config.toml.~/.codex/config.toml [mcp_servers.notion-token] url = "https://mcp.notion.com/mcp" bearer_token_env_var = "NOTION_MCP_TOKEN"Good to know- Codex reads
NOTION_MCP_TOKENfrom your environment each time it connects, so the token stays out of the file.
- Codex reads
Step 2: Check it's connected
Terminal codex mcp listIn a Codex session, run
/mcpto see connected servers and their tools.Step 3: Try a first request
Ask Codex something that only works with Notion (MCP token) connected:
Say to Codex Find the Notion database that tracks our design tasks and list what's due this week.
If it doesn't work
- Codex reads
~/.codex/config.toml. A project.codex/config.tomlis only read in projects you have trusted. - Codex doesn't expand
~or environment variables incommand. Use a full path in the config file. - Servers that need a sign-in: run
codex mcp login <name>.





