Standup from your activity vs Discourse MCP

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

Standup from your activity logoStandup from your activityCommunication · Local subprocess (stdio)Generate your daily standup from real GitHub, Jira, Linear, and Slack activity.37FairAuth: not declaredDiscourse 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 required

Verdict: choose Standup from your activity 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?

Standup from your activity logoChoose Standup from your activity when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GITHUB_TOKEN, JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN, LINEAR_API_KEY, SLACK_TOKEN, SLACK_CHANNELS, STANDUP_NAME.
Explore Standup from your activity

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecStandup from your activity logoStandup from your activityDiscourse MCP logoDiscourse MCP
CategoryCommunicationCommunication
Quality signal37/100 · Fair87/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsGITHUB_TOKENJIRA_BASE_URLJIRA_EMAILJIRA_API_TOKENLINEAR_API_KEYSLACK_TOKENSLACK_CHANNELSSTANDUP_NAMENone listed
Verified ownerCommunity listing Verified
GitHub stars077
Directory activity 0 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
ToolsNot listed16

Tools & capabilities

Standup from your activity tools

No tool names declared yet. Check the project README from 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.

Standup from your activity

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "standup-from-your-activity": {
      "command": "npx",
      "args": [
        "-y",
        "standup-mcp"
      ],
      "env": {
        "GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE",
        "JIRA_BASE_URL": "YOUR_JIRA_BASE_URL_HERE",
        "JIRA_EMAIL": "YOUR_JIRA_EMAIL_HERE",
        "JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN_HERE",
        "LINEAR_API_KEY": "YOUR_LINEAR_API_KEY_HERE",
        "SLACK_TOKEN": "YOUR_SLACK_TOKEN_HERE",
        "SLACK_CHANNELS": "YOUR_SLACK_CHANNELS_HERE",
        "STANDUP_NAME": "YOUR_STANDUP_NAME_HERE"
      }
    }
  }
}

Discourse MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "discourse-discourse-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@discourse/mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Standup from your activity is categorized under Communication and uses a local stdio subprocess. Discourse MCP belongs to Communication and uses a local stdio subprocess. Pick Standup from your activity 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.

Standup from your activity 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 standup-from-your-activity and discourse-discourse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Standup from your activity has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Discourse MCP has 87/100 (Excellent) with 5 views, 0 installs and 77 GitHub stars.