OneNote MCP server
2026년 11월 14일 커밋Microsoft Graph를 통해 AI 클라이언트가 Microsoft OneNote의 노트북 목록 조회, 페이지 검색, 내용 읽기, 페이지 생성 및 삭제를 수행할 수 있도록 합니다.
다른 이름 onelastcommit/onenote-mcp
- 스타
- 0
- Tools
- 11
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 14일
- 라이선스
- MIT
OneNote MCP란?
Microsoft Graph를 통해 AI 클라이언트가 Microsoft OneNote의 노트북 목록 조회, 페이지 검색, 내용 읽기, 페이지 생성 및 삭제를 수행할 수 있도록 합니다. 11개 도구를 제공합니다. 예: list_notebooks, list_sections, list_section_groups.
프로젝트 README에서 생성된 요약
OneNote MCP server 정보
이 MCP server를 사용하면 AI 인터페이스에서 Microsoft OneNote 노트북을 직접 관리할 수 있습니다. Claude Desktop, Cursor 또는 Claude Code와 같은 클라이언트를 통해 개인 또는 조직의 노트를 상호작용할 수 있습니다. Microsoft Graph에 연결하여 노트북 및 섹션 목록 조회, 페이지 전체 텍스트 검색, 특정 페이지 내용 읽기, 페이지/섹션/섹션 그룹 생성 및 삭제를 통한 계층 구조 관리 기능을 제공합니다.
개발자는 stdio 전송 모드를 사용하여 이 server를 로컬에서 실행할 수 있습니다. 이 방식은 서브프로세스로 실행되며 인증 토큰을 로컬 디스크에 보관합니다. claude.ai 웹 또는 모바일 앱을 통한 원격 액세스가 필요한 경우 HTTP 전송 모드를 사용하여 server를 셀프 호스팅할 수 있습니다. 이 설정을 위해서는 Notes.ReadWrite 및 offline_access 권한이 있는 Microsoft Entra 앱 등록이 필요합니다. 인증은 device-code flow를 통해 처리되므로 인증 정보가 안전하게 사용자 제어 하에 유지됩니다.
활용 사례
- 1기존 노트 검색AI 클라이언트에게 모든 OneNote 페이지에 대한 전체 텍스트 검색을 수행하여 특정 정보를 찾도록 요청합니다.
- 2노트북 구조 정리AI에게 노트북, 섹션 또는 섹션 그룹을 생성하여 새로운 조직 계층 구조를 구축하도록 지시합니다.
- 3페이지 내용 추출AI가 특정 페이지의 내용을 HTML 또는 Markdown 형식으로 읽어 데이터를 요약하거나 처리하도록 합니다.
- 4노트 생성 자동화자연어를 사용하여 AI가 특정 섹션 내에 새 페이지를 초안 작성하고 저장하도록 합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
OneNote MCP 도구 11
README에서 감지됨list_notebookslist_sectionslist_section_groupssearch_pagesread_pagecreate_notebookcreate_sectioncreate_section_groupcreate_pageupdate_pagedelete_page
| list_notebooks | — | |
| list_sections | — | |
| list_section_groups | — | |
| search_pages | — | |
| read_page | — | |
| create_notebook | — | |
| create_section | — | |
| create_section_group | — | |
| create_page | — | |
| update_page | — | |
| delete_page | — |
구성
ONENOTE_MCP_CLIENT_IDONENOTE_MCP_HTTP_TOKEN
| 이름 | 설명 | 유형 |
|---|---|---|
| ONENOTE_MCP_CLIENT_ID | — | |
| ONENOTE_MCP_HTTP_TOKEN | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능onelastcommit/onenote-mcp is public and reachablegithub.com/onelastcommit/onenote-mcp ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-11github.com/onelastcommit/onenote-mcp ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음11 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기@onelastcommit/onenote-mcp
Part of One Last Commit: small ideas, taken further than strictly necessary.
This package has moved. It was previously published as
@atomiclabs97/onenote-mcpand then@1percentlabs/onenote-mcp, and is now@onelastcommit/onenote-mcp. If you have an old name in a config file, switch to the new one. The old packages are deprecated and no longer updated. Versions carry on unbroken, so0.2.1is the direct successor to0.2.0.
An MCP server for Microsoft OneNote. Bring your notebooks into Claude, Cursor, and any MCP-compatible client — list notebooks and sections, full-text search across pages, read individual pages, and create or delete pages from natural language. Authentication uses Microsoft's device-code flow against your own Entra ID app registration, so your data and credentials never leave your machine.
Screenshot/demo coming soon — drop a GIF in
docs/images/demo.gifand reference it here.
Two ways to run it
| You want to use OneNote in… | Run mode | Start here |
|---|---|---|
| Claude Desktop, Cursor, Claude Code on your laptop | stdio — the server runs as a subprocess of the client; tokens never leave your disk |
Quick start below |
| claude.ai web + iOS/Android, or any remote client | http — you self-host the server and add it as a Connector |
Remote transport → Self-hosting |
Stdio is the default and needs no hosting. The HTTP transport is opt-in.
Quick start
1. Register a Microsoft Entra app
The server talks to Microsoft Graph using a Microsoft Entra (Azure AD) app registration that you own. This takes about 2 minutes.
Screenshots referenced below live in
docs/images/. They are placeholders today — contributions welcome.
a. Create the registration
-
Go to the Microsoft Entra admin center → App registrations and click + New registration.
-
Name: anything (e.g.
onenote-mcp). -
Supported account types: choose "Accounts in any organizational directory and personal Microsoft accounts" if you want both work and personal OneNote to work; otherwise pick what matches your tenant.
-
Redirect URI: leave blank — the device-code flow doesn't need one.
-
Click Register.

b. Add the API permissions
-
In the new app's left nav, click API permissions → + Add a permission → Microsoft Graph → Delegated permissions.
-
Search for and check both:
Notes.ReadWriteoffline_access
-
Click Add permissions. (No admin consent is required for personal Microsoft accounts. Work/school tenants may need an admin to grant consent for the directory.)

c. Allow the public client flow
The device-code flow is a "public client" flow — it doesn't use a client secret.
-
Go to Authentication in the left nav.
-
Scroll to Advanced settings → Allow public client flows and toggle it Yes.
-
Click Save.

d. Grab the client ID
Back on the app's Overview page, copy the Application (client) ID. You'll pass it to the server via the ONENOTE_MCP_CLIENT_ID environment variable.

2. Sign in
ONENOTE_MCP_CLIENT_ID=<your-app-client-id> npx @onelastcommit/onenote-mcp login
This prints a code and a URL like:
To sign in, use a web browser to open https://microsoft.com/devicelogin
and enter the code ABCD-1234 to authenticate.
Open the URL, paste the code, sign in with the Microsoft account whose OneNote you want to access, and approve the requested permissions. The refresh token is then cached at ~/.config/onenote-mcp/tokens.json (mode 600) so the MCP server can run silently.
To sign out:
ONENOTE_MCP_CLIENT_ID=<your-app-client-id> npx @onelastcommit/onenote-mcp logout
3. Wire it into your MCP client
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"onenote": {
"command": "npx",
"args": ["-y", "@onelastcommit/onenote-mcp"],
"env": {
"ONENOTE_MCP_CLIENT_ID": "your-app-client-id"
}
}
}
}
Restart Claude Desktop. The OneNote tools should appear in the tool picker.
Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"onenote": {
"command": "npx",
"args": ["-y", "@onelastcommit/onenote-mcp"],
"env": {
"ONENOTE_MCP_CLIENT_ID": "your-app-client-id"
}
}
}
}
Anything else
Any MCP-compatible client that supports stdio servers will work. Run npx @onelastcommit/onenote-mcp with ONENOTE_MCP_CLIENT_ID set in the environment.
Remote transport (HTTP)
In addition to the default stdio mode, the server can speak the MCP Streamable HTTP transport. Use this when the MCP client lives somewhere other than the same machine as the server — for example, claude.ai Connectors (web, iOS, Android), a self-hosted bridge on a home server, or a backend integration.
Stdio is still the default. Nothing changes for existing Claude Desktop / Cursor users.
When to use which
| Transport | When |
|---|---|
stdio (default) |
Local desktop clients (Claude Desktop, Cursor, Claude Code). Tokens never leave your disk; the server runs as a subprocess of the client. |
http |
Remote clients (claude.ai web/mobile Connectors), self-hosted deployments, any setup where the server runs separately from the client. |
Boot it
# Generate a strong shared secret first — clients must send this as `Authorization: Bearer <token>`.
export ONENOTE_MCP_HTTP_TOKEN="$(openssl rand -base64 32)"
ONENOTE_MCP_CLIENT_ID=<your-app-client-id> \
npx @onelastcommit/onenote-mcp --transport http --port 3000
The server refuses to start without ONENOTE_MCP_HTTP_TOKEN — a remote MCP endpoint with no auth is the entire world reading your OneNote.
Endpoints
| Method | Path | Auth | Purpose |
|---|---|---|---|
POST / GET / DELETE |
/mcp |
Authorization: Bearer <token> |
MCP Streamable HTTP transport. All tools mounted here. |
GET |
/healthz |
none | Liveness probe; returns 200 with no body. For platform health checks. |
Bearer-token comparison is constant-time. Wrong or missing tokens return 401 Unauthorized with a WWW-Authenticate: Bearer header.
Defaults and overrides
| Flag | Env var | Default | Notes |
|---|---|---|---|
--transport <stdio|http> |
— | stdio |
|
--host <addr> |
ONENOTE_MCP_HTTP_HOST |
127.0.0.1 |
Set to 0.0.0.0 to listen on all interfaces (containers / PaaS). |
--port <n> |
ONENOTE_MCP_HTTP_PORT |
3000 |
Flags win over env vars.
Pointing a client at it
# Sanity check
curl http://127.0.0.1:3000/healthz # → 200
curl -X POST -H "Authorization: Bearer $ONENOTE_MCP_HTTP_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' \
http://127.0.0.1:3000/mcp
Sign in with ONENOTE_MCP_CLIENT_ID=<your-app-client-id> npx @onelastcommit/onenote-mcp login (one-time, on the host running the server) before any tools are invoked — the device-code flow is the same as the stdio path and caches tokens at ~/.config/onenote-mcp/tokens.json. The bearer token is server↔client auth only; the Microsoft Graph credentials still come from the cached refresh token.
On a headless host (a container, a PaaS) there's no terminal for the device-code login. Run login on your laptop instead, then pass the resulting tokens.json to the server via the ONENOTE_MCP_TOKEN_CACHE env var — on first boot in HTTP mode the server seeds its cache from it. The deployment guides walk through this.
Rotating the bearer token
- Pick a new token:
openssl rand -base64 32. - Update
ONENOTE_MCP_HTTP_TOKENand restart the server. - Update the token everywhere a client uses it.
No session state is kept between requests, so rotation is just a restart — there is nothing to migrate.
Multi-tenant?
No. v0.2 assumes one OneNote account per deployment. The bearer token gates access to whichever account onenote-mcp login was last run for on the host. If you need per-user separation today, run one instance per user.
Limitations
- The HTTP transport is stateless: each request gets a fresh transport, no
Mcp-Session-Idis issued, and the server does not push notifications. Tools that perform a single request → single response (i.e. all eleven shipped tools) work normally. - No rate-limiting beyond the bearer-token gate. Put the server behind a reverse proxy / API gateway if you need it.
Self-hosting
To use OneNote from claude.ai (web + mobile) you host the HTTP transport somewhere with a public HTTPS URL, then add it as a custom Connector. Copy-paste recipes:
| Guide | For |
|---|---|
| Fly.io | Fastest path — free-tier eligible, ~10 minutes, HTTPS handled for you. |
| Docker (VPS / home server) | Any host you control; uses the published ghcr.io/onelastcommit/onenote-mcp image. |
| claude.ai Connector | Wiring the deployed URL into claude.ai and verifying the tools. |
Released Docker images are pushed to the GitHub Container Registry on every version tag.
Tools
| Tool | Description | Key inputs |
|---|---|---|
list_notebooks |
Lists all OneNote notebooks for the signed-in user. | (none) |
list_sections |
Lists sections, optionally scoped to a single notebook. | notebookId? |
list_section_groups |
Lists section groups (folders), optionally scoped to a notebook. | notebookId? |
search_pages |
Full-text search across pages (title + content). | query, limit? |
read_page |
Returns page metadata + content (HTML or Markdown). | pageId, format? (html | markdown) |
create_notebook |
Creates a new top-level notebook. | name |
create_section |
Creates a section inside a notebook or section group. | notebookId? | sectionGroupId?, name |
create_section_group |
Creates a section group inside a notebook or another section group. | notebookId? | sectionGroupId?, name |
create_page |
Creates a page in a section. Accepts Markdown (default) or HTML, plus optional binary attachments. | sectionId, title, content, format?, attachments? |
update_page |
Applies edits to a page: append/prepend/insert/replace/delete elements. | pageId, operations[] |
delete_page |
Permanently deletes a page. Irreversible. | pageId |
Configuration
| Env var | Required | Description |
|---|---|---|
ONENOTE_MCP_CLIENT_ID |
yes | Application (client) ID of your Microsoft Entra app registration. |
ONENOTE_MCP_TENANT_ID |
no | Tenant ID. Defaults to common, which works for both personal and work accounts. |
ONENOTE_MCP_HTTP_TOKEN |
http only | Shared bearer token for the HTTP transport. Required when --transport http. |
ONENOTE_MCP_HTTP_HOST |
no | Bind address for the HTTP transport. Defaults to 127.0.0.1. --host wins. |
ONENOTE_MCP_HTTP_PORT |
no | Listen port for the HTTP transport. Defaults to 3000. --port wins. |
ONENOTE_MCP_TOKEN_CACHE |
no | Verbatim tokens.json contents used to seed the cache on a headless host. Applied only in --transport http mode when no cached token exists yet. |
XDG_CONFIG_HOME |
no | Override the config directory. Tokens are stored at <dir>/onenote-mcp/tokens.json. |
Known limitations
- Attachments are sent in-memory.
create_pagereads attachment files fully into memory before posting; very large files (~150 MB+) may strain Node's heap. Streamed uploads are a future enhancement. update_pagetargets are rawdata-idselectors. To edit a specific element, read the page first and pull thedata-idattribute out of the returned HTML. Higher-level selectors (e.g. "the section under heading X") are tracked for a follow-up.- Search latency. Microsoft Graph's
$searchagainst/me/onenote/pagescan take a few seconds against large notebooks; the server retries on 429s with exponential backoff.
Contributing
PRs welcome. The codebase aims to stay small and focused.
git clone https://github.com/onelastcommit/onenote-mcp
cd onenote-mcp
yarn install
yarn build
yarn test
yarn typecheck—tsc --noEmit(coverssrc/+scripts/)yarn lint— ESLintyarn test— Vitest (unit tests, mocked Graph)yarn dev— incremental rebuild on save (tsc --watch+tsc-alias --watch);dist/stays runnable
Use Yarn (Classic), not npm. The repo's lockfile is
yarn.lock—package-lock.jsonshould not be committed.
End-to-end smoke test
scripts/smoke.ts exercises every shipped tool against a real OneNote account. It's not in CI — needs real credentials.
# One-time: register an Entra app (see Quick start above) and sign in
ONENOTE_MCP_CLIENT_ID=<your-client-id> yarn build
ONENOTE_MCP_CLIENT_ID=<your-client-id> node dist/cli.js login
# Then run the smoke test
ONENOTE_MCP_CLIENT_ID=<your-client-id> yarn smoke
It's idempotent: reuses (or creates) a notebook called OneNote MCP Smoke Test, walks through 13 steps covering auth, list/search/read/create/update/delete and the multipart attachment path, and cleans up the pages it creates. Sections and section groups are left behind for the next run.
If you're using an AI coding assistant (Claude Code, Cursor, etc.), see CLAUDE.md for project conventions, the arrow-function rule, and the tool-authoring checklist.
Commits follow Conventional Commits (feat:, fix:, chore:, etc.). CI runs typecheck + lint + test + build on every push to main and every PR.
Roadmap
-
update_page— in-place edits via Graph'sPATCHsyntax -
create_section/create_notebook - Image and attachment upload (multipart create_page)
- Section group support (list + create + section-in-group targeting)
- HTTP (Streamable HTTP) transport with bearer-token auth
- Self-hosted deployment guide (Dockerfile + Fly.io recipe + claude.ai Connector validation)
- Streamed attachment uploads (avoid in-memory buffering for large files)
- Resource-style page browsing (alongside the tool surface)
License
MIT © Ahmad Al Mezaal
OneNote MCP 질문
OneNote MCP는 어떤 도구를 제공하나요?
11개 도구를 제공합니다. 예: list_notebooks, list_sections, list_section_groups, search_pages, read_page.
Microsoft 인증은 어떻게 이루어지나요?
사용자의 Entra ID 앱 등록을 대상으로 Microsoft의 device-code flow를 사용합니다. 이를 통해 데이터와 인증 정보가 사용자의 로컬 머신을 벗어나지 않도록 보장합니다.