Discourse MCP vs Gateco

A side-by-side look at the Discourse MCP and Gateco MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Discourse MCP logoDiscourse MCPCommunication · Local subprocess (stdio)Official Discourse MCP server for forum integration. Search topics, read posts, manage categories and tags, discover users, and interact with Discourse communities.87ExcellentAuth: api key requiredGateco logoGatecoCommunication · Local subprocess (stdio)Permission-aware retrieval for AI systems: policy-enforced access to organizational knowledge.52GoodAuth: not declared

Verdict: choose Discourse MCP for communication work as a local process; choose Gateco for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Discourse MCP logoChoose 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.
Explore Discourse MCP

Gateco logoChoose Gateco when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GATECO_API_KEY.
  • You want tools like gateco_retrieve, gateco_ask, gateco_check_access.
Explore Gateco

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDiscourse MCP logoDiscourse MCPGateco logoGateco
CategoryCommunicationCommunication
Quality signal87/100 · Excellent52/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingFreeNot declared
Required env varsNone listedGATECO_API_KEY
Verified owner VerifiedCommunity listing
GitHub stars770
Directory activity 5 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools167

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

Gateco tools 7

  • gateco_retrievePermission-aware retrieval (vector/keyword/hybrid/grep)
  • gateco_askGrounded answer synthesis with search modes (Team+)
  • gateco_check_accessDry-run access simulation (Growth+). **User session only** (`gateco login`); not callable with an API key
  • gateco_list_connectorsList connectors with readiness levels
  • gateco_list_principalsList identity principals
  • gateco_list_groupsList groups (IdP-synced and local directory) with live member counts. Works with a `retrieve`-scoped key against a backend from 2026-10-02 on; older backends answer that a user session is needed
  • gateco_resolve_principalResolve a principal by email or provider subject

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "discourse-discourse-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@discourse/mcp@latest"
      ]
    }
  }
}

Gateco

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gateco": {
      "command": "uvx",
      "args": [
        "gateco"
      ],
      "env": {
        "GATECO_API_KEY": "YOUR_GATECO_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Discourse MCP is categorized under Communication and uses a local stdio subprocess. Gateco belongs to Communication and uses a local stdio subprocess. Pick Discourse MCP for communication work and Gateco 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. Gateco has no declared pricing — check the project's own site. 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 gateco 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. Gateco has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.