Mailtrap vs Discourse MCP
A side-by-side look at the Mailtrap and Discourse MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mailtrap for communication work as a local process; choose Discourse MCP for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mailtrap when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MAILTRAP_API_TOKEN, MAILTRAP_ACCOUNT_ID, DEFAULT_FROM_EMAIL, MAILTRAP_SANDBOX_ID, MAILTRAP_TEST_INBOX_ID, MAILTRAP_ORGANIZATION_ID, MAILTRAP_ORGANIZATION_API_TOKEN. - You want tools like
send-email, batch-send-transactional-email, batch-send-bulk-email.
Choose Discourse MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
discourse_select_site, discourse_search, discourse_filter_topics.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 64/100 · Good | 87/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | MAILTRAP_API_TOKENMAILTRAP_ACCOUNT_IDDEFAULT_FROM_EMAILMAILTRAP_SANDBOX_IDMAILTRAP_TEST_INBOX_IDMAILTRAP_ORGANIZATION_IDMAILTRAP_ORGANIZATION_API_TOKEN | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 66 | 77 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 125 | 16 |
| Full listing | View Mailtrap | View Discourse MCP |
Tools & capabilities
Mailtrap tools 125
send-emailSend an email to your recipient email address using Mailtrap Email API. You can send emails to multiple recipients at once.batch-send-transactional-emailSend a batch of transactional emails in one Mailtrap API call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Each request must include `to`.batch-send-bulk-emailSend a batch of bulk emails (Mailtrap bulk-stream API) in one call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Each request must include at least one of `to`/`cc`/`bcc`.create-templateCreate a new email templatelist-templatesList the account's email templates with page-token pagination (`token`, `per_page`). Pages are offsets over the newest-first list, so after deleting templates list again from token 1 instead of continuing with the next token.get-templateGet a single email template by ID, including subject, category, and HTML/text body.update-templateUpdate an existing email templatedelete-templateDelete an existing email templatesend-sandbox-emailSend an email in sandbox mode to a test inbox without delivering to your recipientsbatch-send-sandbox-emailSend a batch of emails in sandbox mode to a test inbox in one Mailtrap API call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Requires `sandbox_id` or the MAILTRAP_SANDBOX_ID env var.get-sandbox-messagesGet list of messages from the sandbox test inboxshow-sandbox-email-messageShow sandbox email message details and content from the sandbox test inbox. Optionally include spam report (SpamAssassin score) and HTML analysis (client compatibility) for email testing workflows.- +113 more on the listing page
Discourse MCP tools 16
discourse_select_siteValidate and select a Discourse site. Returns JSON with site URL and title.discourse_searchSearch site content. Returns JSON object with results array of matching topics (id, slug, title) and meta (total, has_more).discourse_filter_topicsDiscover topics through a filtered, top, or hot view. Filtered uses Discourse TopicsFilter syntax; top uses Discourse's authoritative top score and defaults to weekly; hot is defined exactly as daily top (not sentiment, controversy, or real-time velocity). Returns a uniform rich topic projection and truthful pagination metadata.discourse_read_topicRead topic metadata and posts. Large post limits can require multiple upstream requests. For moderation queues, prefer reviewable list/detail evidence instead of fanning this tool out across flagged topics.discourse_read_postRead a specific post. Returns JSON with id, topic_id, post_number, username, created_at, and raw content.discourse_read_topic_postsRead exact, earliest, latest, around-post, or username-filtered topic evidence. Selection is bounded to 50 posts and reports the visible stream size without claiming the entire topic was loaded.discourse_search_postsSearch post-level evidence with Discourse query syntax. Unlike discourse_search, this preserves matched posts, highlighted blurbs, authors, topics, categories, and truthful bounded continuation. This is keyword search, not Discourse AI semantic search.discourse_get_userGet user info. Returns JSON with id, username, name, trust_level, created_at, bio, admin, and moderator.discourse_list_user_postsGet paginated list of user posts/replies. Returns JSON object with posts array (id, topic_id, post_number, slug, title, created_at, excerpt, category_id) and meta (page, limit, has_more).discourse_list_usersList users via admin API. Requires admin API key. Returns ~100 users per page (Discourse's fixed page size). Returns JSON with users array and pagination meta.discourse_get_chat_messagesGet messages from a chat channel. Returns JSON object with channel_id, messages array (id, username, created_at, message, edited, thread_id, in_reply_to_id), and meta.discourse_get_draftRetrieve a specific draft by key. Returns JSON with draft_key, sequence, and parsed data (title, reply, categoryId, tags, action).- +4 more on the listing page
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.
Mailtrap
{
"mcpServers": {
"mailtrap": {
"command": "npx",
"args": [
"-y",
"mcp-mailtrap"
],
"env": {
"MAILTRAP_API_TOKEN": "YOUR_MAILTRAP_API_TOKEN_HERE",
"MAILTRAP_ACCOUNT_ID": "YOUR_MAILTRAP_ACCOUNT_ID_HERE",
"DEFAULT_FROM_EMAIL": "YOUR_DEFAULT_FROM_EMAIL_HERE",
"MAILTRAP_SANDBOX_ID": "YOUR_MAILTRAP_SANDBOX_ID_HERE",
"MAILTRAP_TEST_INBOX_ID": "YOUR_MAILTRAP_TEST_INBOX_ID_HERE",
"MAILTRAP_ORGANIZATION_ID": "YOUR_MAILTRAP_ORGANIZATION_ID_HERE",
"MAILTRAP_ORGANIZATION_API_TOKEN": "YOUR_MAILTRAP_ORGANIZATION_API_TOKEN_HERE"
}
}
}
}
Discourse MCP
{
"mcpServers": {
"discourse-discourse-mcp": {
"command": "npx",
"args": [
"-y",
"@discourse/mcp@latest"
]
}
}
}
Frequently asked questions
Mailtrap is categorized under Communication and uses a local stdio subprocess. Discourse MCP belongs to Communication and uses a local stdio subprocess. Pick Mailtrap for communication work and Discourse 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.
Mailtrap has no declared pricing — check the project's own site. Discourse MCP is listed as free. 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 mailtrap and discourse-discourse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mailtrap has a quality signal of 64/100 (Good) with 0 views, 0 installs and 66 GitHub stars. Discourse MCP has 87/100 (Excellent) with 5 views, 0 installs and 77 GitHub stars.