Local Mcp
Give Claude Code or Cursor native control over Mail, Calendar, Teams, and OneDrive on your Mac without brittle AppleScript glue.
Overview
local-mcp is an MCP server for the Build phase that connects coding agents to 82 native macOS tools for Mail, Calendar, Teams, and OneDrive.
What is this MCP server?
- 82 native macOS tools across Mail, Calendar, Microsoft Teams, and OneDrive
- stdio npm package local-mcp v3.0.9 for Claude Desktop and Claude Code
- Runs on-device for mail and calendar workflows without cloud scraping
- Targets indie builders who live in Mail + Calendar while shipping side projects
- 82 tools documented in server description
- Version 3.0.9 via npm identifier local-mcp
- Transport stdio per MCP server schema
Community signal: 16 GitHub stars.
What problem does it solve?
Solo builders on Mac waste time context-switching between their agent and Mail, Calendar, and Teams instead of letting the agent act on those apps directly.
Who is it for?
Mac-based indie developers who want agent-driven inbox, calendar, and Teams actions while coding.
Skip if: Windows or Linux users, teams needing audited enterprise MDM policies, or builders who only need browser-based Gmail.
What do I get? / Deliverables
After you register local-mcp, your agent can query and act on local mail, calendar, Teams, and OneDrive through MCP tool calls from Claude Code or Cursor.
- stdio MCP connection to 82 macOS productivity tools
- Agent-callable Mail, Calendar, Teams, and OneDrive operations
- On-machine workflows without exporting inbox data to a third-party SaaS
Recommended MCP Servers
Journey fit
Solo builders wire local productivity apps into their coding agent during product work, not during ideation alone. This is an MCP integration layer between the agent and macOS services—classic build-phase agent tooling.
How it compares
Native macOS MCP integration with 82 tools, not a generic shell-script skill or a cloud-only mail API wrapper.
Common Questions / FAQ
Who is local-mcp for?
Solo and indie builders on macOS who use Claude Code, Cursor, or Claude Desktop and want Mail, Calendar, Teams, and OneDrive wired into their agent.
When should I use local-mcp?
Use it during build and operate work when you need the agent to read mail, schedule events, or touch OneDrive or Teams without leaving the IDE.
How do I add local-mcp to my agent?
Install the npm package local-mcp, add a stdio MCP server entry pointing at that binary in Claude Code or Cursor settings, then grant macOS permissions the apps require.