How to connect Granola to Hermes Agent
Connect Granola to Hermes with ClawLink in one click — 6 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
GranolaOAUTH2MCPAI meeting notes and transcripts. Once connected, Hermes Agent can read and act on Granola from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Granola access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Granola setup: pair once in the browser and your always-on Hermes agent can act on Granola for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Granola.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Granola
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Granola?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Granola in the ClawLink dashboard — a one-click OAuth approval, no API keys.
Verify the connection by asking Hermes:
Use Granola to mcp get account info and walk me through the result in plain English.
Using a different agent?
The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Granola is connected in the dashboard, that agent calls the same 6 Granola tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Granola MCP for Hermes
Looking for a Granola MCP server for Hermes Agent? ClawLink connects Granola to Hermes Agent and exposes 6 Granola tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Granola integration works the same way.
What the Hermes Agent Granola integration can do
6 Granola tools are ready for Hermes Agent once the account is connected.
All 6 Granola tools for Hermes
| Tool | What it does |
|---|---|
Mcp get account info granola_mcp_get_account_info | Get the email, active workspace, and effective note-access scopes for the Granola account |
Mcp get meeting transcript granola_mcp_get_meeting_transcript | Get the full transcript for a specific Granola meeting by ID |
Mcp get meetings granola_mcp_get_meetings | Get detailed meeting information for one or more Granola meetings by ID |
Mcp list meeting folders granola_mcp_list_meeting_folders | List the user's Granola meeting folders |
Mcp list meetings granola_mcp_list_meetings | List the user's Granola meeting notes within a time range |
Mcp query granola meetings granola_mcp_query_granola_meetings | Query Granola about the user's meetings using natural language |
Try it: find the Granola tool you need
Browse the 6 Granola tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Granola to mcp get account info and walk me through the result in plain English.
Use Granola to mcp get meeting transcript and walk me through the result in plain English.
Use Granola to mcp get meetings and walk me through the result in plain English.
Use Granola to mcp list meeting folders and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Granola working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Granola app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Granola through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Granola. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Granola actions to the runtime in a format your agent can reliably use. | 6 tools for Granola are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Granola to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Granola in the browser, and the 6 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Granola
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Connection succeeds but no tools appear
Reconnect Granola from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Granola tools
Granola tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Granola call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Granola returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
OAuth finished in the browser but the account is still missing
Try reconnecting Granola and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a Hermes Agent Granola integration?
Yes. ClawLink is the fastest way to connect Hermes to Granola: link your Granola account once in the browser and Hermes Agent can call the Granola API through 6 ready-made tools — no custom code or token handling.
How do I connect Granola to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Granola in the dashboard and Hermes can use it from the next message — no config files or API keys to manage.
How long does it take to connect Granola to Hermes Agent?
About two minutes. Sign in, click Connect next to Granola in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Granola up myself?
The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Granola working from chat.
Hermes paired but still can't use Granola
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
