cloud-connectors
Monorepo of MCP connectors for personal cloud services (Microsoft and iCloud), enabling access to Outlook Mail, OneDrive, iCloud Mail, and iCloud Drive via natural language.
README
cloud-connectors
Monorepo of MCP connectors for personal cloud services, packaged as one-click Claude Desktop extensions (.mcpb). Built for eventual marketplace publishing: each connector ships separately with its own credential model and privacy story; shared plumbing lives in a core package.
Packages
| Package | What | Auth |
|---|---|---|
packages/core |
@cloud-connectors/core — shared MCP skeleton: stdio bootstrap, tool-result/error helpers, retry-aware fetch, file utils, HTML→text |
— |
packages/windows-live-connector |
Personal Microsoft Account: Outlook Mail + OneDrive via Microsoft Graph (19 tools) | OAuth 2.0 + PKCE, tokens in DPAPI/Keychain |
packages/icloud-connector |
iCloud: Mail via IMAP/SMTP + iCloud Drive via the local sync folder (17 tools) | Apple app-specific password (stored in OS keychain by Claude Desktop, sensitive user_config) |
Build & pack
$env:PATH = "C:\tools\nodejs;$env:PATH"
npm install # workspace install at repo root
npm run build # core -> windows-live -> icloud, deterministic order
node scripts/pack-mcpb.mjs windows-live-connector # -> dist-bundle/windows-live-connector-<ver>.mcpb
node scripts/pack-mcpb.mjs icloud-connector # -> dist-bundle/icloud-connector-<ver>.mcpb
scripts/pack-mcpb.mjs exists because npm workspaces hoist dependencies to the root node_modules (and symlink core), which would break mcpb pack's self-contained-bundle assumption. It stages the target package with a real npm install --omit=dev (core injected as a tarball) and packs from the staging dir.
Bundles install by double-clicking the .mcpb / dragging it onto Claude Desktop (Settings → Extensions). Per-connector setup (Entra app registration, Apple app-specific password) is documented in each package's README/manifest description.
Note: a .mcpb built on Windows carries Windows-only native bindings for the secure token store (keytar); on macOS both connectors fall back to permissions-restricted plaintext storage with a logged warning. Repack on a Mac for Keychain-backed storage there.
History
Grew out of the standalone project where I tinkered with windows live connectivity because I live in that eco system in addition to Google and Apple.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.