Connect Granola to OpenCode
Give OpenCode governed access to Granola’s 7 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Granola to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode 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 OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Granola’s 7 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode 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 OpenCode
Granola’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
7 Granola tools in OpenCode
Runlayer policy decides which of these OpenCode 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 OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every Granola call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more
