Whooshly MCP Server

Whooshly MCP server exists for a simple reason — assistants are far more useful when they can act on Whooshly directly instead of describing what you should do. Create short links, QR codes, UTM templates, and vCards from your AI assistant.

What you get

The server is hosted – there's nothing to run for URL-based clients. This npm package is a small stdio bridge for clients that don't yet speak remote MCP (e.g. Claude Desktop) and for npx convenience.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Whooshly is connected, these are the calls the assistant has available:

• get_billing_status — Check whether the account has unlocked Core / Pro
• create_link — Create a short link → id, slug, short URL
• list_links — List your links, newest first (cursor-paged)
• get_link_stats — Exact click/scan totals + daily series for a link
• create_qr — Create a dynamic QR code, returned as a scannable PNG
• get_qr — Re-fetch a saved QR code as a PNG
• create_utm — Save a reusable UTM template
• list_utm — List saved UTM templates
• create_vcard — Create a hosted digital business card (vCard) page
• create_page — Create a landing page on your subdomain from content blocks
• update_page — Edit a page's blocks, theme, or slug – never deletes
• list_pages — List your landing pages with lead counts

Configuration and credentials

You will need 3 environment variables: WHOOSHLY_TOKEN, WHOOSHLY_MCP_URL, WHOOSHLY_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Whooshly.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the whooshly mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Whooshly's toolset — get_billing_status, create_link, list_links and 11 more — is a fair guide to whether it matches your workflow. It is maintained by co.whooshly; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.