OneNote MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONENOTE_BACKUP_DIR | No | Path to the OneNote local backup directory used for offline reading. Defaults to %LOCALAPPDATA%\Microsoft\OneNote\16.0\Backup. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notebooksA | List all locally available OneNote notebooks. Shows notebook names and how many sections each one has. |
| list_sectionsC | List all sections in a specific notebook. |
| read_sectionA | Read all text content from a specific section of a notebook. |
| search_notesA | Search for text across ALL notebooks and sections. |
| list_all_sectionsA | List ALL sections across ALL notebooks. Useful for getting a complete overview of everything in your OneNote. |
| get_notebook_summaryC | Get a summary of a notebook: its sections and a preview of each section's content. |
| list_live_notebooksA | List notebooks from the running OneNote app (live, not backup files). This uses the OneNote COM API and shows the notebooks currently open in the OneNote desktop app, including their sections. Use this to find where to create new pages. |
| create_pageA | Create a new page in a OneNote notebook section. |
| list_live_pagesB | List pages in a section from the running OneNote app. |
| append_to_pageA | Append content to an existing OneNote page. |
| update_page_contentB | Replace the body content of an existing OneNote page with new HTML formatting. |
| read_live_pageA | Read full text, tables, and hierarchical sub-bullets from a live OneNote page as Markdown or raw XML. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target distinct objects/actions, but there is overlap between local vs. live notebook/section/page listings, such as list_notebooks vs. list_live_notebooks and list_sections vs. list_all_sections. Descriptions clarify the live/local distinction, so an agent can usually choose correctly, but the boundaries are not perfectly crisp.
The set mostly follows a consistent snake_case verb_noun pattern (list_notebooks, read_section, create_page, update_page_content). Minor inconsistency comes from inserting 'live' in some names (read_live_page, list_live_pages, list_live_notebooks) while other local counterparts omit it.
Twelve tools is a well-scoped size for a OneNote server covering notebooks, sections, pages, reading, searching, and writing. Each tool has a plausible role, and the set is not bloated or too thin.
Core read/search/create/update page workflows are covered, but lifecycle operations are notably incomplete: there is no delete page/section/notebook, no rename or move/copy page, and no create notebook/section. These gaps will cause failures for common management requests.