MCP Gateway · Codex
Connect Notion to Codex
Engineering teams use Notion databases as inventories: services, feature flags, API endpoints. Codex can create those databases from the terminal, change their schema as the code evolves, and fill them from a script's output. Agent hooks send each prompt and Notion tool call to Speakeasy, which allows or denies it before Codex runs it.
- Category
- Productivity
- Tools
- 14
- Authentication
- OAuth
- Codex
- CLI and ChatGPT desktop app
Behind the MCP Gateway
Run Notion MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Notion call inspected and logged.
Set up
Add Notion to Codex in 4 steps
- 01
Add Notion from the catalog
An admin finds Notion in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Notion uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Notion
Give teams the
mcp:connectscope on the Notion server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Notion to their gateway on the next call, and removing it takes it away. - 03
Connect Codex
Add the gateway as an MCP server, then log in.
Run the first command with your organization gateway URL.
Run the second command to sign in.
codex mcp add 'speakeasy' \ --url 'https://<organization host>/mcp/gateway/<organization slug>' codex mcp login 'speakeasy' - 04
Sign in and use Notion from Codex
The first time Codex connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Notion needs its own OAuth grant, so each person connects it once. Until they do, Notion calls fail while the rest of the gateway keeps working.
From then on, Notion's tools appear in Codex, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a team, a ChatGPT workspace admin imports the plugin marketplace under Admin > Plugins and sets an installation policy per role. Imported plugins reach nobody until a policy is set.
Use cases
What Codex users do with Notion
Create an inventory database
Ask Codex for a database of every service in the repository. It defines the schema with SQL DDL, and Notion returns the structure for you to check.
Change a database's schema
When the code gains a new attribute, such as an owner or a runtime version, Codex adds the matching property to the Notion data source.
Fill a database from script output
Codex runs a script that lists the repository's endpoints and creates one Notion page per endpoint in the database, with its properties set.
Tools
14 tools
Each Notion tool can be allowed or denied per team and role at the MCP Gateway before Codex sees it.
notion-search
Perform a search over: - "internal": Semantic search over Notion workspace and connected sources (Slack, Google Drive, Github, Jira, Microsoft Teams, Sharepoint, OneDrive, Linear). Supports filtering by creation date and creator. - "user": Search for users by name or email.
notion-fetch
Retrieves details about a Notion entity (page, database, or data source) by URL or ID. Provide URL or ID in id parameter. Make multiple calls to fetch multiple entities. Pages use enhanced Markdown format.
notion-create-pages
Overview Creates one or more Notion pages, with the specified properties and content. Parent All pages created with a single call to this tool will have the same parent. The parent can be a Notion page ("page_id") or data source ("data_source_id").
notion-update-page
Overview Update a Notion page's properties or content. Properties Notion page properties are a JSON map of property names to SQLite values. For pages in a database: - ALWAYS use the "fetch" tool first to get the data source schema and the exact property names.
notion-move-pages
Move one or more Notion pages or databases to a new parent.
notion-duplicate-page
Duplicate a Notion page. The page must be within the current workspace, and you must have permission to access it. The duplication completes asynchronously, so do not rely on the new page identified by the returned ID or URL to be populated immediately.
Control
What Speakeasy can see and stop in Codex
The gateway covers every client the same way. The rest depends on what Codex exposes to Speakeasy.
Tool logs
Gateway
Every Notion call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Notion tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Notion can reject a tool request before it reaches the server, or withhold a result from Codex. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Codex
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Codex runs it.
User attribution
Codex
An [otel] block in ~/.codex/config.toml sends telemetry to Speakeasy. Export is off by default.
Budgets
Codex
Spend limits can block Codex traffic once a budget is reached.
Device agent and MDM
Codex
The device agent keeps Codex's configuration in sync on managed laptops.
- Codex cloud tasks and GitHub code review run off the device. Neither the plugin nor OpenTelemetry covers them; OpenAI's Compliance Logs record them after the fact.
- The workspace rollout needs a ChatGPT Business, Enterprise or Edu admin.
Questions
Frequently asked questions
How is Notion activity in Codex attributed to a developer?
Who can roll out Notion in Codex across a team?
How do Codex users get Notion?
Are Notion calls from Codex logged?
Connect more