OneNote MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
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 13 tools
Each tool has a clearly distinct purpose targeting specific OneNote operations like listing notebooks, creating pages, or modifying content. There is no overlap or ambiguity between tools like 'createPage', 'updatePageContent', and 'replaceTextInPage' as they handle different aspects of page management.
All tool names follow a consistent verb_noun pattern with clear, descriptive actions (e.g., 'listNotebooks', 'createPage', 'updatePageTitle'). The naming is uniform throughout, using camelCase consistently without any deviations or mixed conventions.
With 13 tools, this server is well-scoped for managing OneNote operations, covering authentication, notebook listing, page creation, content updates, and search. Each tool serves a distinct function, and the count is appropriate for the domain without being excessive or insufficient.
The toolset provides comprehensive coverage for core OneNote workflows, including CRUD operations for pages and notebooks, content manipulation, and search. Minor gaps might include operations like deleting pages or managing sections, but agents can likely work around these with the available tools.