Calendar Bridge

io.github.IsaiahDupreePublished by GitHub account IsaiahDupreev1.3.0Updated Oct 24, 2026

Connects ChatGPT to your Apple Calendar via a local Mac agent + Vercel relay

VerifiedStreamable HTTPWeb executableProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

Connects ChatGPT to Apple Calendar through a hosted relay and a small agent on your own Mac, letting the assistant list, search, read and edit events.

What you can do
  • List calendars and upcoming events in a date window, optionally limited to one calendar
  • Search events by keyword in the title and read a single event by id
  • Create events with title, start, end, location, notes, calendar and all-day flag
  • Update existing event fields, overwriting the fields passed
When to use it
Useful when you want an assistant to look up or add appointments in your Apple Calendar from a chat, while the actual calendar data stays on your Mac. It suits people who keep their schedule in Calendar.app and are comfortable running a background agent on that machine.
Requirements
A remote MCP endpoint with OAuth sign-in, plus a CalendarBridge account and pairing code. A Mac with Node 18+ running the calendar-agent CLI, kept awake and online with the agent running. macOS must be allowed to let the terminal control Calendar. Self-hosting instead needs a Vercel account and a Supabase project with its own environment variables.
Before you install
The connector reads and writes your real calendar events, and update calls overwrite the fields passed, so events should be read first. Write tools are marked destructive so the client can ask before changes. The relay temporarily stores job payloads, and the agent token is kept in a file in your home directory. Self-hosting requires a Supabase service-role key and a JWT secret.

Installation

In SourceWeft

  1. Open Calendar Bridge in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.IsaiahDupree%2Fcalendar-bridge/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "calendar-bridge": {
      "type": "http",
      "url": "https://calendarbridge.vercel.app/mcp"
    }
  }
}

README

📅 CalendarBridge

Your Apple Calendar, in ChatGPT — on your own Mac.

[License: MIT] [npm]

CalendarBridge is a Model Context Protocol (MCP) connector that lets ChatGPT work with your Apple Calendar. Reads execute locally and requested results pass through the authenticated relay — every action runs on your own Mac through a tiny local agent. The cloud piece is only a stateless relay that shuttles requests between ChatGPT and your Mac.

  ChatGPT  ──OAuth──►  CalendarBridge relay  ──job queue──►  calendar-agent  ──►  Calendar.app (connector)          (Vercel, stateless)      (your Mac, polls & executes)     (on your Mac)

Your Mac is the only place your events are ever read or written. The relay stores only short-lived job payloads and your account record; it never sees an event unless a job is in flight, and jobs expire in seconds.

For users — 3 steps

1. Create your account at calendarbridge.vercel.app and generate a pairing code.

2. Install the Mac agent (needs Node 18+):

bash
npx calendar-agent pair <YOUR-CODE>   # link this Mac to your accountnpx calendar-agent install            # keep it running on every restart

The first time it touches Calendar, macOS asks "Terminal wants to control Calendar" — click OK (one time).

3. Connect ChatGPT: Settings → Plugins → turn on Developer mode (Security & login) → Create a custom plugin → paste the MCP Server URL https://calendarbridge.vercel.app/mcp → Authentication OAuth → sign in & Allow.

That's it. In a new chat: "Search my Apple Calendar for the dentist appointment" or "Add a Team Standup to my Work calendar tomorrow at 9am."

Your Mac must be awake with the agent running. npx calendar-agent install makes it start automatically at login and restart if it ever crashes.

Managing the agent

bash
npx calendar-agent status      # is it paired & reachable?npx calendar-agent logs        # recent activitynpx calendar-agent uninstall   # stop auto-start

What ChatGPT can do

ToolAction
list_calendarsList all your calendars (Work, Personal, Family, …)
list_eventsList upcoming events in a date window (default next 7 days), optionally one calendar
search_eventsFind events whose title contains a keyword
get_eventRead one event by id
create_eventCreate an event (title, start, end, optional location, notes, calendar, all-day)
update_eventEdit an event's fields (overwrites the fields you pass — read it first)

Self-hosting

You can run your own relay so nothing depends on the hosted instance.

Prereqs: a Vercel account and a Supabase project (free tiers are fine).

  1. Storage — in your Supabase project's SQL editor, run supabase/schema.sql. It creates a tiny Redis-shaped KV + queue surface (nb_* functions) with RLS on.
  2. Deploy the server/ directory to Vercel.
  3. Set env vars (see server/.env.example):
    • SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY — your project + service-role key
    • JWT_SECRET — openssl rand -hex 32
  4. Verify: curl https://YOUR-APP.vercel.app/api/health → redisConfigured, redisOk, jwtSecretSet all true.
  5. Point the agent at it: npx calendar-agent pair <CODE> --server https://YOUR-APP.vercel.app.

How it works

  • Auth — OAuth 2.1 with PKCE and Dynamic Client Registration (RFC 7591). ChatGPT registers itself, the user signs in on the CalendarBridge consent page, and ChatGPT gets a scoped MCP access token. JWTs are HMAC-signed; three kinds (session, agent, mcp) with distinct privileges. Optional email verification via Resend (RESEND_API_KEY); off unless configured, and enforcement is opt-in (REQUIRE_EMAIL_VERIFICATION).
  • Relay — MCP tool call → job pushed to jobs:<user> (TTL ≤ the caller's wait window, so an abandoned job can't run late) → the Mac agent (holding a hanging long-poll) is handed the job within ~200ms, executes it, pushes the result → the MCP handler returns it. The long-poll means jobs are delivered on arrival rather than on a fixed interval, so relay overhead is ~300ms instead of ~1s. The agent is considered "online" only while it's actively connected.
  • Agent — a dependency-free Node CLI. Tools run via JXA (osascript -l JavaScript) against Calendar.app; arguments are passed as JSON over argv (never shell-interpolated). A macOS LaunchAgent keeps it alive across logins and crashes.

Repository layout

server/    Vercel functions: OAuth + MCP endpoint + relay        (deploy this)agent/     calendar-agent — the npm-published Mac CLI                 (users npx this)kit/       Browser automations: register the dev-mode connector AND           fill the OpenAI directory submission (see kit/README.md)supabase/  schema.sql for self-hosting the storagetest/      end-to-end OAuth + MCP integration test

Development

bash
# servercd server && cp .env.example .env.local   # fill in, then: vercel dev# end-to-end test against a live deployment (reads ../.env.local)node test/e2e-oauth.mjs# agent unit testsnode --test agent/test-agent-unit.mjs

Security & privacy

  • Events are read/written only on your Mac. The relay temporarily stores requested content in short-lived job/result queues — job payloads live in Redis-shaped storage with a short TTL and are deleted on delivery.
  • The agent token is stored at ~/.calendarbridge-agent.json (mode 600).
  • No secrets are committed; see .gitignore and the .env.example files.
  • Write tools are marked destructive so ChatGPT asks before changing an event.

License

MIT © Isaiah Dupree

Production storage and owner verification

Relay 1.4 uses isolated service-role-only tables/functions on the configured shared Supabase project. Production refuses missing storage configuration, bounds RPC requests to ten seconds, and returns HTTP 503 when storage or signing configuration is unavailable. Apply the checked-in isolated-storage migration before deploying this version; it does not replace another bridge's account tables or functions.

node --env-file=.env.local test/live-storage.mjs verifies the actual persistent store, FIFO, expiry and counters using temporary integration keys. BRIDGE_SESSION_FILE=/private/owner-session.json BRIDGE_READ_TOOL=READ_TOOL node test/live-relay.mjs verifies the actual owner session, PKCE OAuth, hosted MCP and paired-Mac read; choose this bridge's inventory tool. No reviewer data counts as a live acceptance. Credentials and sessions belong outside Git.

Source: README.md at commit 71d0ea9

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts