Discourse MCP vs Sequenzy MCP
A side-by-side look at the Discourse MCP and Sequenzy MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Discourse MCP for communication work as a local process; choose Sequenzy 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 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.
Choose Sequenzy 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 have the keys it needs:
SEQUENZY_API_KEY. - You want tools like
get_account, select_company, get_app_urls.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 87/100 · Excellent | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | SEQUENZY_API_KEY |
| Verified owner | Verified | Community listing |
| GitHub stars | 77 | 2 |
| Directory activity | 5 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 16 | 80 |
| Full listing | View Discourse MCP | View Sequenzy MCP |
Tools & capabilities
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
Sequenzy MCP tools 80
get_accountGet account info, available companies, current key permissions, and the API Keys management URL.select_companySet the active company for future tool calls.get_app_urlsBuild dashboard URLs for campaigns, landing pages, sequences, emails, settings, subscription management, domains, and sent email details. `settingsTab: "billing"` resolves to Account -> Subscription.create_companyCreate a new company or brand.get_companyRead company details, product info, brand context, localization, reply-tracking settings, current From/Reply-To defaults, and the effective read-only `emailBranding` entitlement with plan/status reason and subscription URL; STO is explicitly identified as campaign-only.update_companyEdit product info, brand context, email theme, reply tracking, and account-wide From/Reply-To profile defaults or names.get_sync_rulesRead the company's event-to-tag rules and whether it uses the inherited platform preset.update_sync_rulesReplace all sync rules; pass `[]` to disable them or `null` to opt into the SaaS/ecommerce platform preset.get_shopify_automation_settingsRead browse-abandonment, cart-abandonment, and price-drop settings for the connected Shopify store.update_shopify_automation_settingsPartially update Shopify automation settings or reset an individual section to its platform defaults.create_api_keyCreate a company API key and return its one-time secret on standard MCP; omitted from the OpenAI-reviewed route.request_api_key_handoffPrepare an owner-reviewed create/rotation URL when the active key cannot manage API keys itself.- +68 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.
Discourse MCP
{
"mcpServers": {
"discourse-discourse-mcp": {
"command": "npx",
"args": [
"-y",
"@discourse/mcp@latest"
]
}
}
}
Sequenzy MCP
{
"mcpServers": {
"sequenzy-mcp": {
"command": "npx",
"args": [
"-y",
"@sequenzy/mcp"
],
"env": {
"SEQUENZY_API_KEY": "YOUR_SEQUENZY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Discourse MCP is categorized under Communication and uses a local stdio subprocess. Sequenzy MCP belongs to Communication and uses a local stdio subprocess. Pick Discourse MCP for communication work and Sequenzy 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.
Discourse MCP is listed as free. Auth: api key required. Sequenzy 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 discourse-discourse-mcp and sequenzy-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Discourse MCP has a quality signal of 87/100 (Excellent) with 5 views, 0 installs and 77 GitHub stars. Sequenzy MCP has 60/100 (Good) with 3 views, 0 installs and 2 GitHub stars.