Outlook MCP Server

Created By
Wallisking1991a year ago
Overview

what is Outlook MCP Server?

Outlook MCP Server is a Model Context Protocol (MCP) server that provides access to Microsoft Outlook email functionality, allowing LLMs and other MCP clients to read, search, and manage emails through a standardized interface.

how to use Outlook MCP Server?

To use the Outlook MCP Server, clone the repository, install the required dependencies, and configure your MCP client (like Claude Desktop) to connect to the server. Start the server using the command python outlook_mcp_server.py.

key features of Outlook MCP Server?

  • Folder Management: List available mail folders in your Outlook client
  • Email Listing: Retrieve emails from specified time periods
  • Email Search: Search emails by contact name, keywords, or phrases with OR operators
  • Email Details: View complete email content, including attachments
  • Email Composition: Create and send new emails
  • Email Replies: Reply to existing emails

use cases of Outlook MCP Server?

  1. Managing and organizing emails in Outlook through an MCP client.
  2. Automating email retrieval and responses for applications.
  3. Integrating email functionalities into other software solutions.

FAQ from Outlook MCP Server?

  • Can I use Outlook MCP Server on any operating system?

No, it requires Windows operating system with Microsoft Outlook installed.

  • What version of Python is needed?

Python 3.10 or later is required to run the server.

  • What limitations does the server have?

It currently supports text emails only, with a maximum email history limit of 30 days.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Wallisking1991
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

16 hours ago
Voyei

6 hours ago