Qr Agent Core vs Whooshly MCP
A side-by-side look at the Qr Agent Core and Whooshly MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Qr Agent Core for communication work as a local process; choose Whooshly 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?
Choose 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.
Choose Whooshly MCP when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
WHOOSHLY_TOKEN. - You want tools like
get_billing_status, create_link, list_links.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 59/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | API_KEYBASE_URL | WHOOSHLY_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 37 | 15 |
| Full listing | View Qr Agent Core | View Whooshly MCP |
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
Whooshly MCP tools 15
get_billing_statusCheck whether the account has unlocked Core / Procreate_linkCreate a short link → id, slug, short URLlist_linksList your links, newest first (cursor-paged)get_link_statsExact click/scan totals + daily series for a linkcreate_qrCreate a dynamic QR code, returned as a scannable PNGget_qrRe-fetch a saved QR code as a PNGcreate_utmSave a reusable UTM templatelist_utmList saved UTM templatescreate_vcardCreate a hosted digital business card (vCard) pagecreate_pageCreate a landing page on your subdomain from content blocksupdate_pageEdit a page's blocks, theme, or slug – never deleteslist_pagesList your landing pages with lead counts- +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.
Qr Agent Core
{
"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"
}
}
}
}
Whooshly MCP
{
"mcpServers": {
"whooshly-mcp": {
"command": "npx",
"args": [
"-y",
"whooshly-mcp"
],
"env": {
"WHOOSHLY_TOKEN": "YOUR_WHOOSHLY_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Qr Agent Core is categorized under Communication and uses a local stdio subprocess. Whooshly MCP belongs to Communication and uses a local stdio subprocess. Pick Qr Agent Core for communication work and Whooshly 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. Whooshly 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 benswel-qr-agent-core and whooshly-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. Whooshly MCP has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.