Chatpipe MCP vs Jmap MCP
A side-by-side look at the Chatpipe MCP and Jmap MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Chatpipe MCP for communication work over a hosted endpoint; choose Jmap MCP for communication over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Chatpipe MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
publish_page, list_projects, update_page.
Choose Jmap MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
JMAP_SESSION_URL, JMAP_BEARER_TOKEN. - You want tools like
get_mailboxes, search_emails, get_emails.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 52/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | API key required | API key required |
| Pricing | Freemium | BYOK (pay the provider) |
| Required env vars | None listed | JMAP_SESSION_URLJMAP_BEARER_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 178 |
| Directory activity | 5 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 4 | 12 |
| Full listing | View Chatpipe MCP | View Jmap MCP |
Tools & capabilities
Chatpipe MCP tools 4
publish_pagePublish HTML content as a live, shareable page. Returns a public URL.list_projectsList all published pages with their URLs, names, and access levels. Takes no parameters.update_pageUpdate the HTML content of an existing page. The URL remains the same.delete_pagePermanently remove a published page.
Jmap MCP tools 12
get_mailboxesList mailboxes/folders with their IDs, names, and metadata. **Call this first**search_emailsSearch emails with filters. **All filters are AND'd together.** Returns onlyget_emailsRetrieve specific emails by their IDs. Use `properties` to request only what youget_threadsGet email threads by their IDs. Thread IDs come from `get_emails` responsesget_email_changesGet IDs of emails created, updated, or destroyed since a previous state. Use theget_search_updatesGet changes within a previous search query since its `queryState`. Must use themark_emailsMark emails as read/unread or flagged/unflagged.move_emailsMove emails to a different mailbox. Use `get_mailboxes` to find the targetpatch_email_mailboxesAdd or remove selected mailbox memberships without replacing unspecifieddelete_emailsDelete emails permanently (cannot be undone). Prefer moving to Trash viasend_emailSend a new email. Requires either `textBody` or `htmlBody` (or both).reply_to_emailReply to an existing email. Automatically sets To/CC, Re: subject prefix, and
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Chatpipe MCP
{
"mcpServers": {
"darktw-chatpipe-mcp": {
"url": "https://api.chatpipe.net/mcp"
}
}
}
Jmap MCP
{
"mcpServers": {
"wyattjoh-jmap-mcp": {
"url": "https://api.fastmail.com/jmap/session"
}
}
}
Frequently asked questions
Chatpipe MCP is categorized under Communication and uses a remote HTTP/SSE transport. Jmap MCP belongs to Communication and uses a remote HTTP/SSE transport. Pick Chatpipe MCP for communication work and Jmap MCP for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Chatpipe MCP is listed as freemium — a free tier with paid plans. Auth: api key required. Jmap MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add darktw-chatpipe-mcp and wyattjoh-jmap-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chatpipe MCP has a quality signal of 52/100 (Good) with 5 views, 0 installs and 1 GitHub stars. Jmap MCP has 60/100 (Good) with 2 views, 0 installs and 178 GitHub stars.