The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Microsoft Onenote listing page.
Microsoft OneNote (Microsoft 365) MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1481+ live data sources.
| Tool | Description |
|---|---|
list_notebooks | List the OneNote notebooks in the signed-in user's Microsoft 365 / OneNote account. Returns each notebook's id, display name, created/last-modified times, and whether it is the default notebook. Use to discover a user's OneNote notebooks before browsing sections or pages. |
list_sections | List the sections in a OneNote notebook (Microsoft 365). Pass a notebook_id to list that notebook's sections, or omit it to list all sections across every notebook. Returns each section's id, display name, and created/last-modified times. Use to navigate a user's OneNote notes before listing pages. |
list_pages | List OneNote pages (Microsoft 365 notes). Pass a section_id to list pages in that section, or omit it to list recent pages across all notebooks (newest first). Optionally filter with a free-text search query. Returns each page's id, title, and created/last-modified times. Use to find a user's OneNote notes/pages before reading their content. |
get_page_content | Get the full HTML content of a single OneNote page (Microsoft 365 note) by its ID. Returns the page body as HTML. Use after list_pages to read a user's OneNote note in full. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/microsoft_onenote/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
Both URLs reach the same gateway and the same 1481+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
The gateway picks the right tool and fills the arguments automatically.
MIT