onenote-mcp
Related Servers
Alternatives to onenote-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that connects AI tools to Microsoft OneNote for Business via the Microsoft Graph API, enabling listing, creating, and updating notebooks, sections, and pages.6MIT
- AlicenseAqualityBmaintenanceMCP server that enables AI assistants to interact with Microsoft OneNote, allowing listing, reading, searching, and creating notes.10MIT
- AlicenseNot gradedqualityBmaintenanceA robust MCP server that transforms OneNote notebooks into an AI-accessible knowledge base for Gemini Spark, enabling natural language queries to list, read, and search notes via Microsoft Graph API.MIT
- AlicenseNot gradedqualityBmaintenanceA secure MCP server for Microsoft OneNote via the Graph API, enabling listing/reading notebooks, sections, and pages, with optional gated write tools. Read-only by default and deployable to Azure Container Apps.33 npmMIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server that lets AI assistants read and edit OneNote pages on Windows via COM automation, without cloud authentication.1MIT
- AlicenseNot gradedqualityDmaintenanceA pure-local Microsoft OneNote MCP server for Windows that controls the OneNote desktop app through the local OneNote COM API without needing Azure, Microsoft Graph, API keys, or OAuth.1MIT
TDQS
Scored across 13 tools
Each tool maps to a distinct action: auth status/start/end, structural outline vs flat lists, and page/section operations are clearly separated. The descriptions for getOutline/listNotebooks/listSections explicitly clarify when each should be used, so an agent should not confuse them.
The page and section tools consistently use camelCase verb+Resource (listPages, createPage, deletePage, appendToPage, createSection). The auth tools break that pattern slightly with authStatus, authenticate, and signOut, but the overall naming style remains predictable.
Thirteen tools is well within the ideal range and covers authentication, structure discovery, and page/section operations without unnecessary bloat. The three auth tools are justified by the async sign-in flow, and even the slight overlap between getOutline and the list helpers serves different query needs.
Core workflows are covered: authenticate, discover structure, list/search/read/create/append/delete pages, and create sections. Missing full page content replacement and notebook/section deletion are workable gaps, but appendToPage and createSection handle the most common note-taking operations.