OneNote MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONENOTE_BACKUP_DIR | No | The directory where OneNote backup files (.one) are stored. By default, the server reads from the OneNote desktop app's local backup directory (C:\Users\<user>\AppData\Local\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. |
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 10 tools
Most tools have clear, distinct purposes (e.g., create_page vs append_to_page). However, there is potential confusion between list_notebooks and list_live_notebooks, and between list_sections and list_all_sections, though descriptions clarify some differences.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., list_live_notebooks, create_page, search_notes). No mixing of conventions.
With 10 tools, the set is well-scoped for a Note-taking server. It covers the main operations—listing, creating, reading, appending, and searching—without being overwhelming.
Core read (list notebooks, sections, pages, read section) and write (create page, append content) operations are present. However, missing update (edit page), delete (page, section, notebook), and create section/notebook leave notable gaps for full lifecycle management.