Microsoft OneNote
Read and manage Microsoft OneNote notebooks, sections, section groups and pages through the Microsoft Graph OneNote API.
About
Microsoft OneNote ships in the w6w first-party pack. It declares 15 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.onenote- Version
- 0.1.1
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity · Documents & Files
Overview
Microsoft OneNote organizes notes into notebooks, sections, section groups and pages, and this app reaches all four through the Microsoft Graph OneNote API. Unlike this pack’s sibling SharePoint and Excel apps, the OneNote API is documented for BOTH a work-or-school account and a personal Microsoft account — the overview states it gives access to notebooks ‘in a personal or organization account’ and every one of its permission tables carries a non-empty personal-account row — so this app’s OAuth flow uses the common tenant segment rather than organizations, the same choice the sibling onedrive app makes for the same reason.
It covers the four resources the reference documents, addressable at the signed-in user, another user who shared with them, a Microsoft 365 group, or a SharePoint site: Notebooks — list, get and create (notebooks are read-only past creation; the reference documents no rename or delete). Sections and Section Groups — list (either under a specific parent or flat across the whole location), get and create; both are likewise create-only, with no rename or delete of their own. Pages — list, get metadata, get HTML content, create from an HTML document, apply a batch of insert/append/prepend/replace commands to a page’s HTML, and delete.
Two things worth knowing before using it. First, a page’s HTML content travels as the request body itself (Content-Type: text/html), not wrapped in JSON, both reading and writing — and a page’s title comes from the <title> element inside that HTML, not a separate field. Second, this app accepts HTML text only: the multipart form for embedding binary images/files directly in a page is out of scope, because a w6w Action’s sandboxed ctx.fetch carries its body to the host as text, and bytes above U+007F do not survive that crossing intact (the same limitation the sibling sharepoint app’s Upload File action documents). A remote <img src="https://..."> still works when CREATING a page; Microsoft’s own guide says plainly that an UPDATE cannot use a www link for an image at all, regardless of app.
Build with Microsoft OneNote
Three routes to the same 15 actions. The Workflow tab is generated from Microsoft OneNote's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create Section
create-section Create a new OneNote section directly under a notebook or a section group.
Create Section Group
create-section-group Create a new OneNote section group directly under a notebook, or nested under another section group.
List Pages
list-pages List OneNote pages — under a specific section, or flat across the whole location (most recently modified first).
List Section Groups
list-section-groups List OneNote section groups — under a specific notebook or section group, or flat across the whole location.
List Sections
list-sections List OneNote sections — under a specific notebook or section group, or flat across the whole location.
Update Page Content
update-page-content Apply a batch of insert/append/prepend/replace commands to a page's HTML.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Microsoft OneNote's real ids.
{
"manifestVersion": "2",
"name": "onenote-example",
"steps": [
{
"id": "create-notebook",
"uses": {
"app": "io.w6w.onenote",
"action": "create-notebook",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"displayName": "<displayName>"
}
}
]
}Here are some of the things you can do
-
Create Notebook
performcreate-notebook -
Create Page
performcreate-page -
Create Section
performcreate-section -
Create Section Group
performcreate-section-group -
Get Notebook
readget-notebook
+10 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Microsoft OneNote, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Microsoft OneNote. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "create-notebook",
payload: {
// location: "<value>",
// locationId: "<value>",
displayName: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action create-notebook --payload '{"displayName":"<value>"}'Give an AI agent Microsoft OneNote — without giving it Microsoft OneNote's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.onenote#create-notebook",
"input": {
"displayName": "<displayName>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Microsoft OneNote connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Microsoft OneNote's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Microsoft OneNote itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Microsoft OneNote declares its own checks, so its health is a property of the app rather than something the host guesses at.