Onenote MCP Server

If you want an AI assistant working directly with Onenote MCP, the onenote mcp mcp server is the bridge. OneNote MCP Server Implementation with Device Code Authentication.

What Onenote MCP does

A Model Context Protocol (MCP) server implementation that enables AI language models like Claude and other LLMs to interact with Microsoft OneNote.

Key capabilities

• Authentication with Microsoft OneNote using device code flow (no Azure setup needed)
• List all notebooks, sections, and pages
• Create new pages with HTML content
• Read complete page content, including HTML formatting
• Extract text content for AI analysis and summaries
• Summarize content of all pages in a single operation
• Read full content of all pages in a readable format
• Search across your notes

Tools it exposes

Once connected, the assistant can call these 9 tools directly:

• authenticate — Start the Microsoft authentication flow
• listNotebooks — Get a list of all your OneNote notebooks
• getNotebook — Get details of a specific notebook
• listSections — List all sections in a notebook
• listPages — List all pages in a section
• getPage — Get the complete content of a specific page, including HTML formatting
• createPage — Create a new page with HTML content
• searchPages — Search for pages across your notebooks
• Prerequisites — The Prerequisites tool exposed by this server

Installing the onenote mcp mcp server

The server is distributed via npm as npm, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Requirements

• Node.js 16 or higher (install from nodejs.org) - An active Microsoft account with access to OneNote - Git (install from git-scm.com)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Onenote MCP sits in that group, and the shape of its toolset — authenticate, listNotebooks, getNotebook among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• With 9 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Onenote MCP.
• Maintained by danosb, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the onenote mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.