MCP OneNote Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOKEN_CACHE_PATH | No | Path to store MSAL token cache. Default is './token_cache.json'. | ./token_cache.json |
| ANTHROPIC_API_KEY | Yes | Anthropic API key for Claude Vision. | |
| MICROSOFT_CLIENT_ID | Yes | Azure AD Application (client) ID. | |
| MICROSOFT_TENANT_ID | No | Azure AD tenant ID. Default is 'common'. | common |
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 |
| list_sectionsB | List sections in a notebook |
| list_pagesA | List pages in a section |
| read_contentA | Read the HTML content of a page |
| create_notebookB | Create a new OneNote notebook |
| create_sectionA | Create a new section in a notebook |
| create_pageA | Create a new page in a section |
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 7 tools
Each tool targets a distinct resource and action: notebooks, sections, pages, and page content are clearly separated. The hierarchy is obvious from the names and descriptions, so an agent should rarely confuse one tool with another.
Most tools follow a consistent verb_noun pattern such as list_notebooks and create_page. read_content is a slight departure since it refers to a page action but does not include 'page' in the name, though it remains clear and readable.
Seven tools is well-scoped for a OneNote MCP server focused on navigating and creating notebooks, sections, and pages. Each tool covers a necessary operation without redundancy or bloat.
The create and read/list side of the domain is covered well, but there are no update or delete operations for notebooks, sections, or pages. This creates notable gaps for editing or cleaning up content, though basic browsing and creation workflows are functional.