MCP Hey MCP Server

Most team communication work still happens through a UI a human drives. MCP Hey MCP server moves it into the conversation instead. A local MCP server providing Claude with read/write access to Hey.com email accounts via reverse-engineered web APIs.

The short version

mcp-hey has two moving parts: a Bun/TypeScript MCP server that exposes Hey tools over stdio, and a small Python helper that uses the system webview to capture session cookies at login. Everything runs locally — no cloud relay, no credentials stored, just session cookies on disk.

• Read emails from Imbox, Feed, Paper Trail, Set Aside, Reply Later, Drafts, Trash, and Spam
• Download attachments and parse calendar invites from emails
• Send and reply to email threads
• Search emails across boxes
• Organise mail (set aside, reply later, screen in/out, bubble up)
• Local SQLite cache for faster repeated reads and full-text search

The tools it exposes

The server publishes 10 tools. What each one is for:

• Category — Tools
• Read — hey_list_emails (imbox, feed, paper_trail, trash, spam, drafts), hey_imbox_summary, hey_list_set_aside, hey_list_reply_later, hey_list_screener
• Send — hey_send_email, hey_reply, hey_forward
• Triage — hey_set_aside, hey_unset_aside, hey_reply_later, hey_remove_reply_later, hey_move_to, hey_set_status, hey_mark_unseen, hey_mark_seen
• Screener — hey_screen, hey_screen_by_id
• Search — hey_search
• Cache — hey_cache_status
• Prerequisites — The Prerequisites tool exposed by this server
• Installation — 1. A system webview opens with Hey.com's login page. Log in normally. 2. The helper captures session cookies to data/hey-cookies.json (permissions
• Cursor — The Cursor tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What it needs from you

• Bun 1.1 or later - Python 3.10 or later (plus UV if you want to follow the Python tooling in CLAUDE.md) - A Hey.com account - Platform: developed and tested on macOS and Linux. Windows users will likely need WSL — pywebview's Windows backend is not currently exercised.

How it compares

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Hey's toolset — Category, Read, Send and 7 more — is a fair guide to whether it matches your workflow. It is maintained by sealjay; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Hey's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Hey.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.