m365-mcp: OpenClaw Skill with 43 Tools for Outlook, Calendar, OneDrive, Teams, and Tasks
A developer frustrated with incomplete Microsoft 365 integrations for AI agents built their own OpenClaw skill: m365-mcp. It exposes 43 tools across Outlook mail, Calendar, Contacts, OneDrive, Teams, and Tasks, using Microsoft Graph as the backend.
Why build another MCP server?
The author tested several existing Outlook/M365 MCP implementations and found common shortcomings:
- Some covered only email, ignoring Calendar, Contacts, and other services.
- Tool design was awkward or inconsistent across operations.
- Many felt like demos rather than production-ready components.
Instead of patching around these gaps, they wrote their own skill. The hardest part wasn't getting Graph to respond — it was deciding what an AI agent should be allowed to do and where access should stop.
Key design decisions
The skill enforces per-agent trust boundaries. For example, the main OpenClaw agent can use M365 tools, but the coding agent cannot — because they have different jobs and different risk profiles.
This separation is a reminder that AI integrations need explicit access control, not just broad API keys.
Availability
The skill is published on GitHub and ClawHub as m365-mcp. If you're using OpenClaw and need reliable M365 access, you can grab it from there.
The author notes that what started as "I'll just find an existing integration" turned into another software project — a familiar story for anyone who's tried to extend AI agents into enterprise services.
📖 Read the full source: r/openclaw
👀 See Also
ClawCut: A Python Proxy That Makes Small Local LLMs Usable with OpenClaw
ClawCut is a Python Flask proxy that solves common problems when connecting 7B/14B local models to OpenClaw, including context poisoning, infinite loops, and failed cron job outputs. It implements dynamic amnesia during tool calls and auto-delivery for scheduled tasks.
AI Trading Agent with Risk Guardrails for Educational Investing
A developer built an AI-powered trading assistant that connects Claude to a brokerage account with a risk engine between the AI and money. The system includes safety checks like blocking trades that exceed 50% of portfolio allocation, automatic shutdown at 3% daily loss, and a kill switch at 20% drawdown.
Persistent Indexes Over Extraction: Architecture for a YouTube MCP Server
A developer shares architecture notes for building a YouTube MCP server that uses persistent local indexes instead of the common extract-and-forget pattern. Key decisions include a three-tier fallback system, SQLite + sqlite-vec for vector storage, embedding provider abstraction, and a separate visual search index.
AI Token Monitor: macOS Tool Tracks Local Claude Usage and Cost
A developer built AI Token Monitor, a macOS menu bar app that reads local Claude session files to track token usage, model distribution, and cost equivalents without API keys. The open-source tool revealed 6.5M tokens ($4,924 at API pricing) over 35 days in one user's case.