Skopa MCP is a Personal MCP Server built for developers juggling multiple projects, multiple accounts, and multiple AI assistants. It exposes your real working context — Google Calendar, Outlook, Gmail, Google Tasks, GitHub pull requests, GitLab merge requests, across every account you connect — as a standard Model Context Protocol endpoint. Any MCP-compatible client (Claude Desktop, Claude Code, Cursor, ChatGPT, Gemini, or a custom agent) can read your schedule, your tasks, and your review queue, and act on them through secure tool calls.
Connect one or many Google Calendar accounts and a Microsoft Outlook account. Claude, Cursor, or any MCP client can read, search, filter, create, update, and delete events across all of them — with multi-account colour-coding and smart authuser linking so multi-org workflows keep working.
Google Tasks integration with multi-list, multi-account support. The LLM can create, complete, reorder, and clean up tasks across every task list you own — scoped by account, respecting per-list positions and hierarchy.
OAuth into GitHub and GitLab (PAT fallback supported). Pull requests where you are reviewer or assignee, merge requests across orgs, draft PR flags, and latest-activity timestamps — all readable to the LLM. The copilot finally sees the review queue.
Your email account becomes structured context the LLM can reference without dragging the entire inbox into the prompt. Ask Claude to find the thread where the infra decision was made; it gets the exact thread, not a dump.
Developers running three projects at once lose an hour a day to context-switching. Skopa MCP gives every LLM client a single uniform view of your working context — same schedule, same tasks, same PRs — so you stay in flow instead of re-loading state.
Bearer-token auth with configurable session duration (1 day, 7 days, 30 days, or unlimited). Every MCP client gets a scoped token you can revoke without touching the rest of your integrations.
Claude Desktop, Claude Code, and Cursor have first-class integration with documented setup paths. ChatGPT, Gemini, and any generic MCP client work through the SSE endpoint with Bearer-token auth.
Read, search, and filter your calendar events (Google + Outlook). Create, update, complete, reorder, and delete tasks (Google Tasks). View your assigned and reviewer PRs (GitHub) and MRs (GitLab), including draft flags and latest activity. Reference email threads as structured context. Every action is a typed MCP tool call, not an unstructured prompt.
OAuth for every provider — no password storage. Bearer tokens are short-lived by default (1 day) and scoped to a single MCP client session; revoke a token and that client loses access without touching any other integration. Tokens can be extended to 7 days, 30 days, or unlimited per your risk tolerance.
Skopa MCP aggregates multiple accounts across multiple providers into one server. One Claude Desktop config, one Cursor MCP setup, and the LLM sees every calendar, every task list, every repo review queue — including the ones you normally have to context-switch between. Single-provider connectors solve single-account problems; Skopa solves multi-project flow.
Because the real question developers ask is not "what do I need to do today" — it is "what do I need to do today, given that three PRs are blocked on my review and the infra window is Friday". A copilot that sees your review queue alongside your calendar can actually plan the day; one that only sees calendar cannot.
No. Skopa runs two separate offerings: a boutique AI consultancy (enterprise AI cost optimisation, architecture, integration) and Skopa Personal MCP Server (this product). Use either or both independently.