Outlook Calendar MCP Server

Created By
kgatilina year ago
MCP server for accessing Outlook Calendar events via API
Overview

What is Outlook Calendar MCP Server?

Outlook Calendar MCP Server is a Model Context Protocol (MCP) server that provides read-only access to Outlook/Microsoft 365 calendar events via an API.

How to use Outlook Calendar MCP Server?

To use the server, you need to authenticate with your Microsoft 365 account and then you can retrieve calendar events using the provided API endpoints.

Key features of Outlook Calendar MCP Server?

  • Read-only access to Outlook calendar events
  • On-demand authentication flow
  • Command-line interface for testing and interaction
  • Configuration via YAML files or environment variables

Use cases of Outlook Calendar MCP Server?

  1. Integrating calendar data into AI assistants.
  2. Building applications that require calendar event retrieval.
  3. Automating calendar event management tasks.

FAQ from Outlook Calendar MCP Server?

  • Can I modify my calendar events using this server?

No, the server only provides read-only access to calendar data.

  • What are the prerequisites for using this server?

You need Go 1.21 or higher, a Microsoft 365 account, and a registered application in Azure AD with the appropriate permissions.

  • Is there a command-line interface available?

Yes, there is a CLI client for testing and interacting with the MCP server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kgatilin
Star
0
Language
Go
License
-

Recommend Servers

View All
Gpt Scrambler

2 days ago
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.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago