Qr Agent Core vs Imap MCP Server

A side-by-side look at the Qr Agent Core and Imap MCP Server 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 requiredImap MCP Server logoImap MCP ServerCommunication · Local subprocess (stdio)IMAP/SMTP MCP server to search, read, organize, send, reply & forward email for AI assistants71GreatAuth: other

Verdict: choose Qr Agent Core for communication work as a local process; choose Imap MCP Server 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

Imap MCP Server logoChoose Imap MCP Server when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You want tools like imap_add_account, imap_update_account, imap_list_accounts.
Explore Imap MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecQr Agent Core logoQr Agent CoreImap MCP Server logoImap MCP Server
CategoryCommunicationCommunication
Quality signal59/100 · Good71/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredother
PricingFreemiumFree
Required env varsAPI_KEYBASE_URLNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3111
Directory activity 2 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
Tools3740

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

Imap MCP Server tools 40

  • imap_add_accountAdd a new IMAP account configuration
  • imap_update_accountUpdate an existing IMAP account. Useful for fixing SMTP settings without removing and re-adding the account.
  • imap_list_accountsList all configured IMAP accounts
  • imap_remove_accountRemove an IMAP account configuration
  • imap_connectConnect to an IMAP account
  • imap_disconnectDisconnect from an IMAP account
  • imap_test_accountTest an existing account connection without re-entering credentials. Validates IMAP connectivity and returns folder count and message count.
  • imap_search_emailsNote: on some servers a 'flagged' or starred message carries a custom keyword (e.g. an Open-Xchange color label or Apple's $MailFlagBit*) instead of, or in addition to, the \Flagged system flag. After any flagged search, inspect each result's customKeywords field before concluding a message is or isn't flagged — do not rely on the flagged filter alone. Search for emails matching criteria (sender, recipient, subject, body text, date range, read/flagged status). Use this to FIND messages when you know something about them but not their UID — e.g. "emails from amazon last week", "unread invoices". By default searches a single folder (INBOX). Set searchAllFolders=true to scan every mailbox at once — this catches messages filed away by rules (e.g. a receipt routed to a custom folder); Trash/Spam/Drafts are skipped unless you opt in. By default returns lightweight headers (uid, from, subject, date, and folder when searching across folders); set `includeBody=true` to also return the parsed body in one round-trip instead of paying the N+1 cost of calling imap_get_email per match. For the newest messages without criteria, prefer imap_get_latest_emails.
  • imap_get_emailRead the FULL content of a single email by its UID (body, sender/recipients, date, attachment list, optional raw headers and text-attachment previews). By default the body is returned as clean Markdown in markdownContent and raw HTML is omitted so it never crosses the boundary; set bodyFormat to "html" for the legacy raw htmlContent, or "text" for plain text only. Use after imap_search_emails or imap_get_latest_emails gives you a uid. Body text is truncated to maxContentLength to protect the context window — raise it for long messages. To fetch attachment bytes, use imap_download_attachment.
  • imap_upload_fileUpload a file to the server for use as an email attachment. Returns a path that can be used with imap_send_email attachments. This allows sending large attachments without hitting context window limits. Max size: 26214400 bytes (configurable via IMAP_MAX_UPLOAD_SIZE). Uploads are auto-deleted after 86400000 ms (configurable via IMAP_UPLOAD_TTL_MS).
  • imap_download_attachmentDownload a single attachment from an email (folder + uid + attachment filename/contentId, as listed by imap_get_email). Images are returned inline for viewing; PDFs are saved and their text is extracted inline (extractText); other files are saved to the shared downloads directory (or savePath). Use when the user wants the actual file contents, not just the message body.
  • imap_mark_as_readMark one or many emails as read. Accepts a single UID or an array — pass an array to flag N messages in one IMAP STORE round-trip (useful when triaging).
  • +28 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"
      }
    }
  }
}

Imap MCP Server

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

Frequently asked questions

Qr Agent Core is categorized under Communication and uses a local stdio subprocess. Imap MCP Server belongs to Communication and uses a local stdio subprocess. Pick Qr Agent Core for communication work and Imap MCP Server 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. Imap MCP Server is listed as free. Auth: other. 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 imap-mcp-server 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. Imap MCP Server has 71/100 (Great) with 7 views, 0 installs and 111 GitHub stars.