Iconnect
Connect your agent to macOS and Apple services—calendar, reminders, Shortcuts, and more—when you automate a Mac-centric solo workflow.
Overview
io.github.heznpc/iconnect is a Build-phase MCP server for macOS that exposes 123 tools across 14 modules so agents can integrate with the Apple ecosystem over stdio.
What is this MCP server?
- 123 MCP tools organized across 14 Apple-focused modules
- Targets the full Apple ecosystem from a single iconnect-mcp npm server (v0.1.1)
- macOS only—requires Apple APIs and permissions on your Mac
- stdio transport for Claude Code, Cursor, and other MCP clients
- Lets agents read and act on native apps instead of brittle UI scraping
- 14 modules
Community signal: 11 GitHub stars.
What problem does it solve?
Automating Apple apps and system services from an AI agent usually means fragile scripts or manual copy-paste because there is no unified MCP bridge on macOS.
Who is it for?
Solo builders on macOS who want agent-driven shortcuts across Apple apps and system features while building or operating a Mac-first product.
Skip if: Windows or Linux developers, headless CI-only pipelines, or teams that only need cloud SaaS APIs without local Mac access.
What do I get? / Deliverables
After registering iconnect-mcp, your agent can call dozens of native Apple modules from one MCP config on your Mac.
- Agent-callable access to 14 Apple ecosystem MCP modules on your Mac
- Automated reads and actions across permitted native services from chat
- Reduced manual context switching between IDE and Apple apps
Recommended MCP Servers
Journey fit
Build is where you wire native platform bridges; iconnect is an integration MCP for the Apple stack on your dev machine. integrations is the right shelf for ecosystem-wide MCP modules that talk to OS APIs rather than a single REST vendor.
How it compares
macOS native integration MCP, not a cross-platform cloud DevOps connector.
Common Questions / FAQ
Who is io.github.heznpc/iconnect for?
It is for macOS-based indie developers who want their coding agent to reach Apple ecosystem apps and services through MCP instead of one-off AppleScript.
When should I use io.github.heznpc/iconnect?
Use it while building or automating Mac workflows when you need deep OS-level integrations that web APIs do not cover.
How do I add io.github.heznpc/iconnect to my agent?
On macOS, install the iconnect-mcp npm package, add it as a stdio MCP server in your agent settings, grant requested system permissions, and restart the client.