ynesterenk/onenote-mcp-server

OneNote MCP Server

A Model Context Protocol (MCP) server implementation for Microsoft OneNote, enabling AI language models to interact with OneNote through a standardized interface.

Features

Notebook Management

• List all notebooks
• Create new notebooks
• Get notebook details
• Delete notebooks

Section Management

• List sections in a notebook
• Create new sections
• Get section details
• Delete sections

Page Management

• List pages in a section
• Create new pages with HTML content
• Read page content
• Update page content
• Delete pages
• Search pages across notebooks

Installation

Installing from npm (Recommended)

npm install -g mcp-server-onenote

The package is now available on the npm registry as of April 27, 2025.

Running the Package

After installation, you can run the package using:

mcp-server-onenote

Or with npx:

npx mcp-server-onenote

Installing via Smithery

To install OneNote Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @modelcontextprotocol/server-onenote --client claude

Installing from GitHub

npm install -g github:ZubeidHendricks/azure-onenote-mcp-server

Configuration

Set the following environment variables:

• AZURE_TENANT_ID: Your Azure tenant ID
• AZURE_CLIENT_ID: Your Azure application (client) ID
• AZURE_CLIENT_SECRET: Your Azure client secret

Using with MCP Client

Add this to your MCP client configuration (e.g. Claude Desktop):

{
  "mcpServers": {
    "onenote": {
      "command": "mcp-server-onenote",
      "env": {
        "AZURE_TENANT_ID": "<YOUR_TENANT_ID>",
        "AZURE_CLIENT_ID": "<YOUR_CLIENT_ID>",
        "AZURE_CLIENT_SECRET": "<YOUR_CLIENT_SECRET>"
      }
    }
  }
}

Azure App Registration

1. Go to Azure Portal and navigate to App registrations
2. Create a new registration
3. Add Microsoft Graph API permissions:
   • Notes.ReadWrite.All
   • Notes.Read.All
4. Create a client secret
5. Copy the tenant ID, client ID, and client secret for configuration

Development

# Install dependencies
npm install

# Build
npm run build

# Set environment variables (Windows PowerShell)
npm run env:set

# Set environment variables (Linux/macOS/Git Bash)
npm run env:set-bash

# Run with environment setup (Windows)
npm run dev

# Run locally (after setting environment variables)
npm start

# Run tests
npm test

# Lint
npm run lint

Quick Start Scripts

For convenience, the following scripts are provided to set up your Azure environment variables:

Windows PowerShell (set env vars and run):

.\set-env-and-run.ps1

Windows Batch (set env vars and run):

set-env-and-run.bat

Manual setup - Windows PowerShell:

.\set-env.ps1
npm start

Manual setup - Linux/macOS/Git Bash:

source ./set-env.sh
npm start

Using npm scripts:

# Windows (automatically sets env vars, builds, and runs)
npm run dev

# Manual setup
npm run env:set      # Windows PowerShell
npm run env:set-bash # Linux/macOS/Git Bash
npm start

🔐 Secret Management

For security and convenience, the scripts can automatically load your Azure credentials from a secret.local file:

1. Copy the example file:

   cp secret.local.example secret.local
   

2. Edit secret.local with your actual Azure credentials:

   AZURE_TENANT_ID=your-actual-tenant-id
   AZURE_CLIENT_ID=your-actual-client-id
   AZURE_CLIENT_SECRET=your-actual-client-secret
   

3. Run the scripts - they will automatically load from secret.local:

   npm run dev  # or .\set-env-and-run.ps1
   

🔒 Security Features:

• ✅ secret.local is in .gitignore (never committed to git)
• ✅ Scripts fallback to placeholder values if file doesn't exist
• ✅ Supports comments and empty lines in the secret file
• ✅ Works with all environment setup scripts

⚠️ Security Note: Never commit the secret.local file to version control! It's automatically ignored by git.

Contributing

See for information about contributing to this repository.

License

This project is licensed under the MIT License - see the file for details

Changelog

0.1.0 (2025-04-27)

• Initial release
• Core functionality for OneNote notebook, section, and page management
• Published to npm registry

0.1.1 (2025-04-27)

• Added executable bin to package.json
• Fixed issue where npx command couldn't determine executable to run
• Updated README with clear running instructions