OneNote MCP Server

# OneNote Integration Methods for MCP This document outlines various integration methods for connecting your Model Context Protocol (MCP) tool with Microsoft OneNote notebooks. ## 1. Direct Link Access The shared link you provided (`https://1drv.ms/o/c/8255fc51ed471d07/EgcdR-1R_FUggIKOAAAAAAABNwDG_sG8hAEWMbw5HvXy0A?e=blsdDq`) allows anyone to access and edit your notebook through a web browser. This is the simplest integration method. ### How It Works: 1. The link opens your OneNote notebook in a web browser 2. Users can view and edit content directly through the OneNote web interface 3. No complex authentication is required for access ### Limitations: - Limited programmatic control compared to API access - Doesn't provide direct integration with your MCP without additional tooling ## 2. Browser Automation Approach For a tighter integration with your MCP, you can use browser automation tools like Playwright or Puppeteer to interact with the OneNote web interface programmatically. ### Implementation Steps: 1. Set up a browser automation tool (Playwright recommended) 2. Create scripts to: - Navigate to your shared notebook URL - Extract content from specific sections/pages - Add new content to selected locations ### Example Workflow: ```javascript // Conceptual example - would need actual implementation const { chromium } = require('playwright'); async function interactWithOneNote(sharedLink) { const browser = await chromium.launch(); const page = await browser.newPage(); // Navigate to the shared notebook await page.goto(sharedLink); // Wait for the notebook to load await page.waitForSelector('.NotebookPage'); // Extract content (example selector) const pageContent = await page.textContent('.PageContent'); // Perform MCP operations with the content // ... // Add new content (example) await page.click('.AddContentButton'); await page.fill('.ContentInput', 'New content from MCP'); await browser.close(); return pageContent; } ``` ## 3. Hybrid API and Direct Link Approach This approach combines the simplicity of direct link access with limited use of Microsoft Graph API for reading operations. ### Implementation: 1. Use the direct link for primary user access and editing 2. Use Microsoft Graph API with minimal permissions just for reading content 3. Bridge the two approaches through your MCP ### Advantages: - Avoids complex authentication for writing operations - Provides structured data access for reading operations - Works with personal Microsoft accounts without needing admin consent ## 4. WebView Embedding Embed a WebView component directly in your MCP application that loads the shared OneNote interface. ### Implementation: 1. Use Electron, WebView2, or similar technology to embed a web browser 2. Load the shared notebook URL in the embedded browser 3. Use JavaScript to communicate between your MCP and the embedded notebook ### Advantages: - Seamless integration with your MCP UI - No need for complex authentication - Provides a familiar OneNote interface for users ## Recommended Approach For your specific use case, we recommend the **Direct Link + Browser Automation** approach: 1. Use the direct link as the primary access method 2. Implement browser automation scripts for programmatic interaction 3. Create a simple bridge between your MCP and these scripts This approach provides the best balance of simplicity and functionality without requiring complex API authentication or permissions. --- ## Further Resources - [Playwright Documentation](https://playwright.dev/docs/intro) - [Microsoft Graph API for OneNote](https://learn.microsoft.com/en-us/graph/api/resources/onenote) - [OneNote Web App URL Parameters](https://docs.microsoft.com/en-us/office/client-developer/onenote/url-parameters-for-opening-notebooks)