OneNote MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is OneNote MCP Server?

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

how to use OneNote MCP Server?

To use the OneNote MCP Server, install it via npm, configure the necessary Azure environment variables, and integrate it with an MCP client.

key features of OneNote MCP Server?

  • Notebook Management: List, create, get details, and delete notebooks.
  • Section Management: List, create, get details, and delete sections in notebooks.
  • Page Management: List, create, read, update, delete pages, and search pages across notebooks.

use cases of OneNote MCP Server?

  1. Automating note-taking and organization in OneNote.
  2. Integrating AI language models for enhanced note management.
  3. Developing applications that require interaction with OneNote data.

FAQ from OneNote MCP Server?

  • What is required to run the OneNote MCP Server?

You need to set up Azure credentials and install the server using npm.

  • Can I use this server with other applications?

Yes, it can be integrated with any application that supports the MCP protocol.

  • Is there any documentation available?

Yes, detailed documentation is provided in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago