OneNote

An MCP that connects to personal OneNote notebooks via Microsoft Graph, listing notebooks and retrieving page content with credential caching.

javascript

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "swax-onenotemcp": {
      "command": "node",
      "args": [
        "C:\\\\git\\\\azure-onenote-mcp-server\\\\dist\\\\index.js"
      ],
      "env": {
        "AUTH_CACHE_DIR": "C:\\\\git\\\\azure-onenote-mcp-server\\\\.cache",
        "AZURE_CLIENT_ID": "YOUR_AZURE_CLIENT_ID",
        "AZURE_CLIENT_SECRET": "YOUR_AZURE_CLIENT_SECRET"
      }
    }
  }
}

This MCP server provides an integration for OneNote, enabling you to access and work with personal notebooks through the MCP API while caching authentication credentials for improved performance and reliability. It is designed to run locally and be consumed by an MCP client, simplifying access to OneNote data from your tooling.

How to use

You run the local MCP server and connect to it with your MCP client. Start the server after you have registered your Azure app and set the required environment variables. The server authenticates against Microsoft Graph to access your OneNote notebooks and caches the credentials on disk for faster subsequent starts.

How to install

Prerequisites: Install Node.js (LTS version) on your system. You will also need access to an Azure tenant to register a Graph API app.

Set up the Azure app and permissions (Notes.Read, Notes.Read.All; Notes.Write if you want write access with awareness of potential data risks). 2) Create a client secret. 3) Note the client ID and client secret for use in the local environment.
Define the credentials cache location on disk where the access tokens will be stored.
Install dependencies, build, and run the server locally. Follow the exact commands below.
Test the server to verify it starts and can respond to requests from your MCP client.

Additional sections

Azure App Registration steps, local server setup, and client configuration are described below in concrete detail so you can set up and run the MCP server end to end.

{
  "mcpServers": {
    "onenote": {
      "type": "stdio",
      "command": "node",
      "args": ["C:\\git\\azure-onenote-mcp-server\\dist\\index.js"],
      "env": {
        "AZURE_CLIENT_ID": "YOUR_CLIENT_ID",
        "AZURE_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
        "AUTH_CACHE_DIR": "C:\\git\\azure-onenote-mcp-server\\.cache"
      }
    }
  }
}

Security and testing notes

Store credentials securely and use the cache directory to hold tokens; keep secrets out of public repos. Test the server locally by starting it and issuing a test request through your MCP client, ensuring the token cache is created and reused on subsequent runs.

Available tools

listNotebooks

Retrieves the list of personal OneNote notebooks accessible by the authenticated user.

getPageContent

Fetches the contents of a specified OneNote page, streaming content where supported.

Built by

VeilStrat

AI signals for GTM teams