Connect Granola to Codex
Give Codex governed access to Granola’s 7 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Granola to Codex in four steps
Admins approve the server once. Everyone in Codex then gets it through the same governed connection.
- 1
Approve Granola in Runlayer
Add Granola from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Granola’s 7 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex setup guide - 3
Sign in to Granola
Sign in the way Granola requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Granola from Codex
Granola’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
7 Granola tools in Codex
Runlayer policy decides which of these Codex users can call. 4 read data only.
Get account info
Get the email, active workspace, joined workspaces (names and IDs), and effective note-access scopes for the Granola account currently connected to this MCP session.
Get meeting transcript
Get the full transcript for a specific Granola meeting by ID.
Get meetings
Get detailed meeting information for one or more Granola meetings by ID.
List meeting folders
List the user's Granola meeting folders.
List meetings
List the user's Granola meeting notes within a time range.
Query Granola meetings
Query Granola about the user's meetings using natural language.
Switch workspace
Change your saved active Granola workspace.
Control
What Runlayer can see and stop in Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Granola call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more