OneNote MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_CLIENT_ID | No | Azure Application Client ID to authenticate with Microsoft Graph. If not set, the server defaults to using the Microsoft Graph Explorer's public Client ID. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
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 20 tools
Most tools have clearly distinct purposes targeting specific OneNote operations like listing notebooks, creating pages, or searching content. However, some overlap exists between 'searchPages', 'searchPageContent', and 'searchInNotebook', which could cause confusion about their exact scopes without descriptions.
All tool names follow a consistent camelCase pattern with clear verb_noun combinations (e.g., 'createPage', 'listNotebooks', 'updatePageTitle'). The naming convention is uniform throughout the set, making it predictable and readable.
With 20 tools, the count is on the higher side but reasonable for a comprehensive OneNote server. It feels slightly heavy compared to typical well-scoped servers (3-15 tools), but it covers many operations without being extreme.
The tool set provides good coverage for OneNote operations, including CRUD for pages (create, get, update), listing notebooks and sections, and various search functions. Minor gaps might include deleting pages or notebooks, but core workflows are well-supported.