{
  "markdown": "# mcp-microsoft-onenote\n\nMicrosoft OneNote (Microsoft 365) MCP Pack\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1481+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `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. |\n| `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. |\n| `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. |\n| `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. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"microsoft_onenote\": {\n      \"url\": \"https://gateway.pipeworx.io/microsoft_onenote/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/microsoft_onenote/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1481+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Microsoft Onenote data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3481,
  "sha": "ac9707495f805bf9cf1adc6582e60e7a404e4dc8a1881aa91eba6373dd7c0da1",
  "repo_slug": "pipeworx-io/mcp-microsoft-onenote",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_microsoft_onenote_77d8fa7f/readme"
}