The Amie MCP server.
Your calendar, wherever your agent lives.
Give Claude, Codex, Cursor — or any MCP-compatible agent — your calendar, todos, and meeting notes. Schedule events, send invites, manage tasks, and search every transcript, straight from chat — across all your Gmail and Google Calendar accounts, not just one.
Connect in a minute
Amie's MCP server is remote — nothing to install, nothing to run. Point your agent at the URL, sign in with your Amie account when the OAuth prompt appears, and you're connected.
https://mcp.amie.so
claude mcp add amie https://mcp.amie.so -t http
Add the Amie MCP server: it's a remote MCP server named "amie" at https://mcp.amie.so (HTTP transport, sign in via OAuth when prompted). Then confirm it works by listing my next three calendar events.
In Claude on web or desktop, go to Settings → Connectors → Add custom connector and paste the server URL. Cursor, Codex, and other MCP clients work the same way: add a remote HTTP server, approve the sign-in, done.
All your accounts. One server.
Most Gmail and Google Calendar MCP servers authenticate a single account, so your agent only ever sees part of your schedule. Amie supports multiple accounts: connect work and personal Gmail and Google Calendar — as many as you have — and your agent sees all of them through one connection. It checks availability across every calendar, books from the right account, and never asks you to reconnect just to switch contexts.
What your agent can do
One connection covers three surfaces. Your agent reads your meeting notes, transcripts, and action items. It manages your todos — creating, updating, and completing them. And it works your calendar for real: checking availability, creating events, sending invites, and RSVPing on your behalf.
Search meeting notes
Full transcripts
Action items
Create & complete todos
Todo lists & labels
Read your schedule
Create events
Send & suppress invites
RSVP for you
Contact lookup
Google & Outlook
Multiple Gmail & GCal accounts
Calendar view in chat
Works in any MCP client
OAuth 2.1, scoped access
Ask things like
Your agent resolves names to real contacts, checks your actual availability, and books the event — invites included. No copy-pasting schedules into chat, no hallucinated calendars.
Secure by design
The connection uses OAuth 2.1 with PKCE, and every tool call is checked against explicit scopes — meeting notes are read-only, while todo and calendar access is granted separately. Tokens are stored hashed, expire hourly, and can be revoked anytime from Amie's settings. Your agent sees your account and nothing else, and Amie never logs your conversation content.