Discourse MCP vs Ganty MCP

A side-by-side look at the Discourse MCP and Ganty MCP 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 requiredGanty MCP logoGanty MCPCommunication · Remote HTTP/SSEGantt chart SaaS with server-side critical path and dependency-aware shift-impact tools, plus CRUD.55GoodAuth: not declared

Verdict: choose Discourse MCP for communication work as a local process; choose Ganty 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?

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

Ganty MCP logoChoose Ganty MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like list_workspaces, list_projects, create_project.
Explore Ganty MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDiscourse MCP logoDiscourse MCPGanty MCP logoGanty MCP
CategoryCommunicationCommunication
Quality signal87/100 · Excellent55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthAPI key requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars770
Directory activity 5 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools1615

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

Ganty MCP tools 15

  • list_workspacesGet all workspaces the authenticated user is a member of.
  • list_projectsList all projects in a workspace (excluding archived).
  • create_projectCreate a new project in a workspace. Returns the created project. Subject to plan-based project count limits.
  • delete_projectPermanently delete a project. All tasks, milestones, and dependencies inside the project are also removed. This cannot be undone.
  • list_tasksList tasks in a project. Supports optional filtering by name (search), status, and assignee.
  • get_taskGet detailed information about a single task, including assignees and dependencies.
  • list_milestonesList milestones in a project (key dates such as launch or review gates).
  • create_milestoneAdd a milestone (key date) to a project.
  • create_taskCreate a new task in a project. Dates must be in YYYY-MM-DD format. End date is exclusive (a 1-day task has end = start + 1 day).
  • update_taskUpdate fields of an existing task. Only provided fields will be modified.
  • set_task_progressUpdate the progress percentage of a task (0-100). Status is auto-derived: 0=not_started, 1-99=in_progress, 100=done.
  • add_dependencyAdd a finish-to-start dependency between two tasks in the same project.
  • +3 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "discourse-discourse-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@discourse/mcp@latest"
      ]
    }
  }
}

Ganty MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ganty-mcp": {
      "url": "https://ganty.app/api/mcp"
    }
  }
}

Frequently asked questions

Discourse MCP is categorized under Communication and uses a local stdio subprocess. Ganty MCP belongs to Communication and uses a remote HTTP/SSE transport. Pick Discourse MCP for communication work and Ganty 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. Ganty MCP 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 ganty-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. Ganty MCP has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.