Migrating from GongRzhe to PRISM
If you're one of the 1,100+ developers who starred gongrzhe/gmail-mcp-server, you've probably noticed: the project is dead. Last commit August 2025. Seventy-two unmerged PRs. No maintainer activity.
PRISM is a drop-in replacement with 109 tools (vs 12). Migration takes 2 minutes.
Step 1: Install
npm install -g @synthcorp/prismStep 2: Authenticate
prism authYou can reuse your existing Google Cloud OAuth credentials. The difference: PRISM encrypts your tokens with AES-256-GCM instead of storing them as plaintext.
Step 3: Swap your MCP config
{ "mcpServers": { "prism": { "command": "prism" } } }Remove the old GongRzhe entry. Restart Claude Code.
Step 4: Verify
Ask Claude: "List my Gmail labels using PRISM." If it responds with your labels, you're done.
What changes for your prompts
Nothing. Your natural language prompts work the same way. Claude uses PRISM's tools instead of GongRzhe's automatically.
What you gain
| GongRzhe | PRISM | |
|---|---|---|
| Gmail tools | 12 | 109 |
| Last updated | Aug 2025 | Active |
| Credentials | Plaintext JSON | AES-256-GCM |
| Rate limiting | None | Built-in |
| Multi-account | No | Yes |
| Test coverage | None | 97.9% |
Tool mapping
| GongRzhe | PRISM |
|---|---|
| send_email | gmail_send_message |
| read_email | gmail_get_message |
| search_emails | gmail_search_messages |
| list_emails | gmail_list_messages |
| modify_email | gmail_modify_message |
| delete_email | gmail_trash_message |
| create_draft | gmail_create_draft |
| list_labels | gmail_list_labels |
Plus 80 more tools GongRzhe never had: threads, filters, forwarding, delegates, settings, export, attachments, send-as aliases, batch operations, and multi-account management.
Reusing your Google Cloud credentials
export PRISM_CLIENT_ID="your-existing-client-id"
export PRISM_CLIENT_SECRET="your-existing-client-secret"
prism authNo need to create a new Google Cloud project or re-enable APIs.
Questions? Open an issue. We respond. That's the whole point.