# How to connect OneNote to Hermes Agent (paste one key, 87 tools)

> Connect OneNote to Hermes with ClawLink: paste your OneNote key once and 87 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/onenote

Most guides for giving Hermes Agent OneNote 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 OneNote setup: pair once in the browser and your always-on Hermes agent can act on OneNote 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 OneNote.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect OneNote** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead:

```bash
npx -y @useclawlink/cli login          # sign in via browser — no API key to paste
npx -y @useclawlink/cli connect onenote  # connect OneNote (browser OAuth)
npx -y @useclawlink/cli actions onenote  # list available actions
npx -y @useclawlink/cli run onenote <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
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 test
```

Then connect OneNote in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your OneNote account details once.

Verify the connection by asking Hermes:

> Use OneNote to copy onenote group notebook 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:

```bash
npx -y @useclawlink/cli login
```

`login` opens the same browser approval and stores a credential locally. Once OneNote is connected in the dashboard, that agent calls the same 87 OneNote tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent).

## OneNote MCP for Hermes

Looking for a OneNote MCP server for Hermes Agent? ClawLink connects OneNote to Hermes Agent and exposes 87 OneNote tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw OneNote integration](https://claw-link.dev/openclaw/onenote) works the same way.

## What the Hermes Agent OneNote integration can do

87 OneNote tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 87.

### 30 of 87 OneNote tools for Hermes

| Tool | What it does |
|---|---|
| **Copy onenote group notebook** `onenote_copy_onenote_group_notebook` | Copies a OneNote notebook to the Notebooks folder in the destination Documents library. The notebook is copied asynchronously. |
| **Copy onenote site notebook** `onenote_copy_onenote_site_notebook` | Copies a OneNote notebook to the destination site in the SharePoint documents library. |
| **Copy section to notebook for user2** `onenote_copy_section_to_notebook_for_user2` | Copies a OneNote section to a specific notebook for a specified user. Use this action when you need to duplicate an existing OneNote section into a different notebook under a specific user's account. |
| **Copy section to notebook2** `onenote_copy_section_to_notebook2` | Copies a OneNote section to a specific notebook within a SharePoint site. |
| **Copy section to section group** `onenote_copy_section_to_section_group` | Copies a OneNote section from a Microsoft 365 group's notebook into another section group. |
| **Copy section to section group for user** `onenote_copy_section_to_section_group_for_user` | Copies a OneNote section to a specific section group for a specified user. |
| **Copy site page to section3** `onenote_copy_site_page_to_section3` | Copies a OneNote page from a SharePoint site to a destination section. |
| **Copy user page to section** `onenote_copy_user_page_to_section` | Copy a OneNote page from a user's notebook to a specified section. Use this action when you need to duplicate a OneNote page into a different section within a user's Microsoft 365 account. |
| **Count notebooks section groups sections** `onenote_count_notebooks_section_groups_sections` | Gets the count of OneNote sections within a section group in a user's notebook. |
| **Count site notebook section groups sections** `onenote_count_site_notebook_section_groups_sections` | Gets the count of sections within a OneNote section group in a SharePoint site notebook. |
| **Create group notebook** `onenote_create_group_notebook` | Creates a new OneNote notebook within a Microsoft 365 group. Use this action when you need to create a new notebook for storing notes within a specific Microsoft 365 group. |
| **Create group pages** `onenote_create_group_pages` | Creates a new OneNote page in the default section of the default notebook for a Microsoft 365 group. Use this action when you need to programmatically create a new page in a group's OneNote notebook. |
| **Get group sections** `onenote_get_group_sections` | Retrieves a specific OneNote section from a Microsoft 365 group |
| **Get me onenote resources value** `onenote_get_me_onenote_resources_value` | Retrieves the binary content of a OneNote resource by ID from the signed-in user's notebooks |
| **Get me section page content** `onenote_get_me_section_page_content` | Retrieves the HTML content of a specific OneNote page from a section for the signed-in user |
| **Get notebook from web URL** `onenote_get_notebook_from_web_url` | Retrieves a OneNote notebook by using its web URL path |
| **Get notebook section group** `onenote_get_notebook_section_group` | Retrieves a specific section group from a OneNote notebook within a Microsoft 365 group |
| **Get onenote group operations** `onenote_get_onenote_group_operations` | Retrieves the status of a long-running OneNote operation for a group |
| **Get onenote group sections pages** `onenote_get_onenote_group_sections_pages` | Retrieves OneNote page metadata directly by page ID in a Microsoft 365 group |
| **Get onenote site operations** `onenote_get_onenote_site_operations` | Retrieves the status of a long-running OneNote operation for a SharePoint site |
| **Get onenote user page content** `onenote_get_onenote_user_page_content` | Gets the HTML content of a specific OneNote page for a user |
| **Get page** `onenote_get_page` | Retrieves metadata and properties of a specific OneNote page from the authenticated user's |
| **Get recent notebooks** `onenote_get_recent_notebooks` | Retrieves a list of recently accessed OneNote notebooks for the signed-in user |
| **Get section** `onenote_get_section` | Retrieves a specific OneNote section by its ID from the current user's OneNote |
| **Get site onenote pages** `onenote_get_site_onenote_pages` | Retrieves a specific OneNote page from a SharePoint site |
| **Get site pages preview** `onenote_get_site_pages_preview` | Retrieves a text preview of a specific OneNote page from a SharePoint site or the signed-in |
| **Get site sections** `onenote_get_site_sections` | Retrieves a specific OneNote section from a SharePoint site |
| **Get site sections pages** `onenote_get_site_sections_pages` | Compatibility alias for retrieving OneNote page metadata directly by page ID in a SharePoint |
| **Get user notebook** `onenote_get_user_notebook` | Retrieves the properties and relationships of a OneNote notebook by ID for a specific user |
| **Get user operation** `onenote_get_user_operation` | Poll the status of a user's asynchronous OneNote operation |

## Example prompts

**Copy Onenote Group Notebook**

> Use OneNote to copy onenote group notebook and walk me through the result in plain English.

**Copy Onenote Site Notebook**

> Use OneNote to copy onenote site notebook and walk me through the result in plain English.

**Copy Section To Notebook For User2**

> Use OneNote to copy section to notebook for user2 and walk me through the result in plain English.

**Copy Section To Notebook2**

> Use OneNote to copy section to notebook2 and walk me through the result in plain English.

## ClawLink vs. building it yourself

The alternative to ClawLink is usually manual integration 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 OneNote working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Setup flow** | Collect and store the right OneNote credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link OneNote without custom integration screens. |
| **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for OneNote. | 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 OneNote actions to the runtime in a format your agent can reliably use. | 87 tools for OneNote are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes OneNote 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 OneNote in the browser, and the 87 tools above work from chat. There is no SDK and no config file, and the OneNote key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison.

### Hermes paired but still can't use OneNote
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 OneNote 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 OneNote tools
OneNote 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 OneNote 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.

### OneNote 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.

### The setup form accepts credentials but calls still fail
Re-enter the credentials carefully and verify the account-level permissions for OneNote. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles.

### Is there a Hermes Agent OneNote integration?
Yes. ClawLink is the fastest way to connect Hermes to OneNote: link your OneNote account once in the browser and Hermes Agent can call the OneNote API through 87 ready-made tools — no custom code or token handling.

### How do I connect OneNote 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 OneNote in the dashboard and Hermes can use it from the next message — no config files, and the OneNote key you paste is stored server-side instead of in your environment.

### How long does it take to connect OneNote to Hermes Agent?
About two minutes. Sign in, click Connect next to OneNote in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring OneNote up myself?
The alternative to ClawLink is usually manual integration 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 OneNote working from chat.

### Hermes paired but still can't use OneNote
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`.

## Related

- [Outlook tools](https://claw-link.dev/hermes/outlook) — Read mail, manage calendar, and browse contacts
- [Power BI](https://claw-link.dev/hermes/power-bi) — Query datasets and manage reports, dashboards, and workspaces
- [Connect Microsoft Teams](https://claw-link.dev/hermes/microsoft-teams) — Chat, meetings, and team collaboration
