OneNote MCP Server Implementation
Azure onenote mcp server lets Claude, Cursor and other MCP clients work with Azure Onenote directly. OneNote MCP Server Implementation.
A Model Context Protocol (MCP) server implementation for Microsoft OneNote, enabling AI language models to interact with OneNote through a standardized interface.
Once connected, the assistant can call these 4 tools directly:
AZURE_TENANT_ID — Your Azure tenant IDAZURE_CLIENT_ID — Your Azure application (client) IDAZURE_CLIENT_SECRET — Your Azure client secretNotes.ReadWrite.All — Notes.Read.AllThe server is distributed via npm as mcp-server-onenote, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 6 environment variables: AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, YOUR_TENANT_ID, YOUR_CLIENT_ID, YOUR_CLIENT_SECRET. Keep credentials in your client's env block or a secrets manager rather than committing them.
Cloud and DevOps servers put infrastructure on speaking terms with your assistant, so "why is this broken?" is answered from real state rather than a generic checklist. Azure Onenote sits in that group, and the shape of its toolset — AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET among others — tells you what it is really for. Worth comparing against the other cloud devops servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| AZURE_TENANT_ID | Your Azure tenant ID |
| AZURE_CLIENT_ID | Your Azure application (client) ID |
| AZURE_CLIENT_SECRET | Your Azure client secret |
| Notes.ReadWrite.All | Notes.Read.All |
{
"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>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| AZURE_TENANT_ID | Configuration value read at startup. | Optional |
| AZURE_CLIENT_ID | Configuration value read at startup. | Optional |
| AZURE_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| YOUR_TENANT_ID | Configuration value read at startup. | Optional |
| YOUR_CLIENT_ID | Configuration value read at startup. | Optional |
| YOUR_CLIENT_SECRET | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.