onenote_mcp_server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONENOTE_CLIENT_ID | Yes | Azure AD Application (client) ID | |
| ONENOTE_LOG_LEVEL | No | Log verbosity: debug, info, warn, error | error |
| ONENOTE_TENANT_ID | Yes | Tenant ID for the Entra app registration | |
| ONENOTE_CLIENT_SECRET | Yes | Client secret value for the app registration | |
| ONENOTE_USER_PRINCIPAL_NAME | Yes | User principal name whose OneNote notebooks the service accesses |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notebooksA | List all OneNote notebooks accessible to the configured service account. Returns notebook IDs, names, share status, and direct links. |
| list_sectionsA | List all sections in a specific OneNote notebook. Use list_notebooks first to get the notebook ID. |
| create_sectionB | Create a new section in a OneNote notebook for the configured account. |
| create_pageA | Create a new page in a OneNote section. The content should be HTML. Script tags and event handlers are stripped for security. |
| update_pageA | Update an existing OneNote page by applying patch commands. Supports append, prepend, insert, replace, and delete operations on specific elements. Call get_page with include_ids=true first to obtain element IDs for precise targeting. |
| get_pageA | Get the HTML content of a OneNote page. Set include_ids=true to get element IDs needed for targeted update_page commands. |
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 6 tools
Each tool targets a distinct resource (notebooks, sections, pages) and action (list, create, get, update). No overlapping purposes; list_sections and create_section are clearly differentiated by action.
All tool names follow a consistent verb_noun pattern: list_notebooks, list_sections, create_section, create_page, update_page, get_page. No mixed conventions or vague verbs.
Six tools is well-scoped for OneNote management, covering the essential notebook/section/page hierarchy without unnecessary bloat or trivial additions.
The tool set covers the core lifecycle: read notebooks, list/create sections, and create/get/update pages. Minor gaps exist (no delete operations, no rename section), but the primary workflows are supported.