What is the key difference between MCP Hey and Inbox Zero?

MCP Hey belongs to the Communication category with local stdio execution, while Inbox Zero belongs to the Communication category with local stdio execution.

How do I install MCP Hey or Inbox Zero in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Hey and Inbox Zero free or paid?

MCP Hey operates under a Free / Open Source model (other). Inbox Zero operates under a Freemium model (OAuth 2.0).

Which MCP server has more tools and community activity?

MCP Hey lists 6 tools with 5 views and 11 GitHub stars. Inbox Zero lists 6 tools with 1 views and 12,211 GitHub stars.

Can I use both MCP Hey and Inbox Zero together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Hey vs Inbox Zero

In-depth architectural comparison of the MCP Hey and Inbox Zero MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Hey

Communication · Local stdio

Quality: 44/100 (Fair) | Auth: other

Inbox Zero

Communication · Local stdio

Quality: 55/100 (Good) | Auth: OAuth 2.0

Verdict Summary: Choose MCP Hey if you need specialized Communication tools running via a local process. Choose Inbox Zero if your workspace requires Communication integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Hey when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: Read email across Hey mailbox areas, Search with a local SQLite full-text index, Send, reply to, and forward messages.

Explore MCP Hey Details

Choose Inbox Zero when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_ID, MICROSOFT_CLIENT_SECRET, GOOGLE_BASE_URL, MICROSOFT_BASE_URL.
Primary tools included: AI personal assistant for inbox organization and reply drafting, Natural language AI rules for custom email handling, Reply Zero tracking for reply and follow-up management.

Feature & Specification Comparison

Specification	MCP Hey Sealjay Communication	Inbox Zero elie222 Communication
Summary	Local MCP server for Hey.com email. Read, search, send, reply, and manage the screener via locally cached session from Hey's webview auth.	An MCP server for Inbox Zero. Adds functionality on top of Gmail like finding out which emails you need to reply to or need to follow up on.
Category & Scope	Communication

Tools & Capabilities Breakdown

MCP Hey Tools (6)

Read email across Hey mailbox areas

Search with a local SQLite full-text index

Send, reply to, and forward messages

Manage labels, collections, and screener decisions

Download attachments and parse calendar invites

Use local stdio transport without a network listener

Inbox Zero Tools (6)

AI personal assistant for inbox organization and reply drafting

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Hey Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sealjay-mcp-hey": {
      "command": "npx",
      "args": [
        "-y",
        "sealjay-mcp-hey"
      ]
    }
  }
}

Inbox Zero Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "elie222-inbox-zero": {
      "command": "npx",
      "args": [
        "-y",
        "@inbox-zero/cli"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE",
        "MICROSOFT_CLIENT_ID": "YOUR_MICROSOFT_CLIENT_ID_HERE",
        "MICROSOFT_CLIENT_SECRET": "YOUR_MICROSOFT_CLIENT_SECRET_HERE",
        "GOOGLE_BASE_URL": "YOUR_GOOGLE_BASE_URL_HERE",
        "MICROSOFT_BASE_URL": "YOUR_MICROSOFT_BASE_URL_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCP Hey is categorized under Communication and uses a local stdio subprocess. In contrast, Inbox Zero belongs to Communication using local stdio subprocess. Select MCP Hey when you need capabilities focused on communication and Inbox Zero when you require tools for communication.

More alternatives to MCP Hey More alternatives to Inbox Zero Communication category hub Canonical compare URL