Qr Agent Core vs Discourse MCP

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

Qr Agent Core logoQr Agent CoreCommunication · Local subprocess (stdio)Dynamic QR code service for AI agents. Create, update, track, and retarget QR codes without regenerating images. 37 tools covering 11 QR types, one-command install via npx qr-for-agent.59GoodAuth: api key requiredDiscourse 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 Qr Agent Core 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?

Qr Agent Core logoChoose Qr Agent Core 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: API_KEY, BASE_URL.
  • You want tools like create_qr_code, get_qr_code, update_qr_destination.
Explore Qr Agent Core

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.

SpecQr Agent Core logoQr Agent CoreDiscourse MCP logoDiscourse MCP
CategoryCommunicationCommunication
Quality signal59/100 · Good87/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredAPI key required
PricingFreemiumFree
Required env varsAPI_KEYBASE_URLNone listed
Verified ownerCommunity listing Verified
GitHub stars377
Directory activity 2 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools3716

Tools & capabilities

Qr Agent Core tools 37

  • create_qr_codeCreate a new managed QR code with optional custom styling. The QR code points to a short URL that redirects to your target URL. You can change the target URL later without regenerating the QR image. Supports custom colors, dot shapes, corner shapes, and logo embedding.
  • get_qr_codeRetrieve details of an existing QR code by its short ID. Returns the current target URL, metadata, and timestamps.
  • update_qr_destinationChange where an existing QR code redirects to. This is the key 'dynamic link' feature: the QR image stays the same, but scanning it will now go to the new URL. Ideal for updating campaigns, fixing broken links, or A/B testing.
  • list_qr_codesList all managed QR codes with pagination. Returns short IDs, target URLs, labels, and timestamps. Use this to browse or search for existing QR codes.
  • delete_qr_codePermanently delete a QR code and all its scan analytics. The short URL will stop working immediately. This cannot be undone.
  • get_qr_analyticsGet enriched scan analytics for a QR code. Returns total scans, daily trends, device/browser/country/referer breakdowns with percentages, and recent scan events with parsed user-agent and geo data.
  • bulk_create_qr_codesCreate multiple QR codes in a single request (up to 50). Each item supports the same options as create_qr_code. The quota check is all-or-nothing: if the batch would exceed your plan limit, no QR codes are created. Ideal for generating QR codes for product catalogs, event lists, or batch operations.
  • bulk_update_qr_codesUpdate multiple QR codes in a single request (up to 50). Change target URLs and/or labels. Items with non-existent short_id are reported as not_found without failing the whole batch.
  • bulk_delete_qr_codesDelete multiple QR codes and their scan analytics in a single request (up to 50). Items with non-existent short_id are reported as not_found without failing the whole batch.
  • create_vcard_qrCreate a QR code that encodes a contact card (vCard). When scanned by a phone camera, it prompts the user to save the contact. Supports all standard vCard fields and custom QR styling.
  • create_wifi_qrCreate a QR code that encodes WiFi credentials. When scanned by a phone camera, it offers to auto-join the WiFi network. No internet connection needed to join — the credentials are encoded directly in the QR image.
  • update_vcard_qrUpdate the contact details of a vCard QR code. Only works on QR codes created with type='vcard'. Partial updates merge with existing data. Note: updating vCard data changes the QR image content.
  • +25 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.

Qr Agent Core

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "benswel-qr-agent-core": {
      "command": "npx",
      "args": [
        "-y",
        "qr-for-agent"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE",
        "BASE_URL": "YOUR_BASE_URL_HERE"
      }
    }
  }
}

Discourse MCP

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

Frequently asked questions

Qr Agent Core is categorized under Communication and uses a local stdio subprocess. Discourse MCP belongs to Communication and uses a local stdio subprocess. Pick Qr Agent Core 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.

Qr Agent Core is listed as freemium — a free tier with paid plans. Auth: api key required. 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 benswel-qr-agent-core and discourse-discourse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Qr Agent Core has a quality signal of 59/100 (Good) with 2 views, 0 installs and 3 GitHub stars. Discourse MCP has 87/100 (Excellent) with 5 views, 0 installs and 77 GitHub stars.