Mail · Calendar · Tasks

One local surface for the work across your accounts.

Bring work and personal mail, calendars, and task lists to Codex, Claude Code, any MCP agent, and your own terminal. Corresync keeps every account’s identity and authorization isolated while one typed interface helps you find, plan, follow up, and act.

Built around the services you already use: Outlook · Gmail · Google Calendar · Microsoft To Do · Todoist · TickTick · open standards. Routes and capabilities remain explicit per account — explore the provider details.

Get set up in four steps Check my email provider

Sign-in stays in your browser or OS keyring—agents never hold Corresync-managed credentials, and there is no hosted relay. Consequential writes show an exact preview and commit only when you approve.

Install now

One command per platform. Then connect the agent you already use.

macOS · Linux

curl -LsSf https://corresync.org/install.sh | sh

Windows · PowerShell

powershell -NoProfile -Command "irm https://corresync.org/install.ps1 | iex"

Windows · WinGet alternative

winget install --id nkiyohara.Corresync --exact

Next · finish guided setup

corr setup

Setup resumes from current local state, discovers account routes without credentials, and previews both account and agent-host changes before applying them. Sign-in remains a separate choice. Prefer to read before you run? Review install.sh or install.ps1 first. Homebrew, Scoop, native Linux packages, and direct downloads are listed in getting started.

Your working day, one surface

Mail, calendars, and tasks—without changing how you sign in.

Corresync is one local CLI and MCP server for the accounts you already control. Each provider exposes a different set of capabilities, so setup stays explicit and the details remain attached to the account.

Mail

Outlook
Gmail
iCloud Mail
JMAP / IMAP

Calendar

Outlook Calendar
Google Calendar
iCloud
CalDAV

Tasks

Microsoft To Do
Google Tasks
Todoist
TickTick

Explore providers and setup routes

One MCP, every account Work and personal stay isolated; every result keeps its account and provider provenance.

Agents never hold credentials Sign-in lives in a visible browser or the OS keyring. No hosted relay, no remote MCP endpoint.

Preview, then commit Sends and destructive writes return an exact server-enforced review first. Approval is single-use.

Your data, explained

Connect Google with an OAuth client you control.

Create a Desktop OAuth client in your own Google Cloud project, import its downloaded JSON through guided setup, then sign in in your normal browser. The client credential and account grant stay in the OS keyring; Corresync-managed Google OAuth stays disabled. Follow the illustrated setup.

Read the Privacy Policy Read the Terms of Use

After install: three short commands

Choose. Sign in. Ask.

No provider is preselected. Corresync first discovers evidence for your address, adds one explicit account route, and only then lets you start that account’s sign-in.

corr setup you@example.com --alias personal
corr auth login --account personal

Discovery opens nothing. The separate login uses the selected route.

2 · Connect

corr mcp setup codex

Registers the local stdio server with your agent. Restart the client once.

3 · Ask

› What needs my attention
  before noon, across all
  my accounts?

The agent calls typed tools; answers keep each account’s identity.

Walk through the full getting-started guide

Day-one outcomes

What you can ask before your coffee cools.

The CLI and MCP agents share the same typed operations, account isolation, and policy checks—so everything below works both ways.

Search every inbox at once

“Find the quarterly-plan thread—work or personal, I don’t remember which.”

$ corr mail search --all-accounts \
    --query 'subject:"quarterly plan"'
● work · microsoft-owa  Ana Ruiz  Plan review
· personal · jmap   Finance      Plan receipt

A failed account surfaces as an explicit partial result—never silently hidden.

See one agenda

“What does my day look like across both calendars?”

$ corr agenda list --all-accounts \
    --start 2026-07-29T00:00:00Z \
    --end 2026-07-30T00:00:00Z
09:30 work      Design review · Teams
12:30 personal  Dentist

Time zones, calendars, and provider provenance stay attached to every event.

Preview a send before approving it

“Draft the reply to Ana. I’ll approve the send myself.”

› Draft a reply to Ana.
  mail_send
REVIEW · send new message
  to    ana@example.invalid
  body  text/plain · 412 B
Nothing sent until this exact
payload is approved.

The commit must match the reviewed account, recipients, and bytes exactly.

See everything you can do—and every limit—in plain language

Safety you can see

Nothing sends on the first attempt.

A consequential command first returns a review. Approval stays bound to that caller, account, provider, target, payload, expiry, and one use.

review before effect

$ corr mail send --account work \
    --to ana@example.invalid \
    --subject 'Quarterly plan' \
    --body-file reply.txt

REVIEW · send new message
  account  work · microsoft-owa
  to       ana@example.invalid
  body     text/plain · 412 B · sha256 9f2c1a…

Nothing sent. Repeat this exact command
with --approve to commit the review.

Agents get typed tools, never credentials. Passwords, cookies, and OAuth grants have no MCP surface and no configuration field.
Local only. The MCP server speaks stdio on your machine. No hosted relay, no remote endpoint, no telemetry pipeline.
Unknown means stop. An ambiguous remote write is never retried automatically.
Mailbox content is untrusted data. It is never authority to run a command or start an agent.

See the complete safety model in plain language

Bring the route you already use

Provider-native when useful. Standards-first when available.

Mail and calendar routes are selected independently, so one account can pair IMAP/SMTP mail with a CalDAV calendar—or use one native route for both.

Browser-owned

Outlook Web

Keep interactive Outlook sign-in in a dedicated visible browser while supporting typed mail and calendar operations.

Explicit OAuth

Microsoft Graph · Google with your own client

Microsoft Graph accepts a public client you are authorized to use. Gmail, Google Calendar, and Google Tasks use a Desktop client from a Google Cloud project you control.

Open standards

JMAP, IMAP/SMTP, and CalDAV

Use encrypted standards endpoints with an OS-keyring entry or one explicitly approved credential helper reference.

Choose with the details in view. The provider guide shows the exact sign-in route, setup requirements, and account-dependent capabilities before you add anything.

Check an address privately

Local MCP over stdio

Meet your agent where it already works.

Setup writes absolute local paths into the client you choose and never creates a remote endpoint. Every client reaches the same 43 narrow tools.

Codex

corr mcp setup
              codex

Registration plus a bundled plugin and Agent Skill.

Claude Code

corr mcp
              setup claude-code

User or project scope; plugin available.

GitHub Copilot CLI

corr mcp setup github-copilot

Native registration and verification.

More MCP clients

corr mcp --help

gemini-cli, qwen-code, qoder, kimi-code, and generic stdio.

See the exact command for every client

Honest edges

Clear limits are part of the product.

The complete picture—capabilities, limits, and how compatibility claims are backed—is on the features page.

Gmail, Google Calendar, and Google Tasks use your own OAuth client. Guided setup imports a Google Desktop client into the OS keyring before explicit login.
Microsoft Graph is bring-your-own OAuth. Corresync does not operate a token relay.
Windows desktop notifications are unavailable. Queue and approved runner modes remain available.
Capabilities stay account-specific. Setup shows the route and services available to that account instead of guessing from the email brand.

Ready when your inboxes are

Bring your correspondence into one local conversation.

Install in one command. Connect your agent in one more.

Copy the install command Follow the full guide