Whooshly Mcp

co.whooshlyPublished by whooshly.coOfficial publisherv1.1.0Updated Oct 27, 2026

Create short links, QR codes, UTM templates, vCards, and landing pages from your AI assistant.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Business & Commerce

Server details

Identifier: co.whooshly/whooshly-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to whooshly.co, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/co.whooshly%2Fwhooshly-mcp.svg)](https://sourceweft.com/mcp/co.whooshly%2Fwhooshly-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Whooshly lets an assistant create short links, dynamic QR codes, UTM templates, vCards and landing pages, and read click/scan analytics.

What you can do: Create and list short links, and search or fetch link details
Create dynamic QR codes and re-fetch saved ones as PNGs
Save and list reusable UTM templates
Create hosted vCard pages and landing pages from content blocks, edit pages, and list or inspect pages with lead counts
Read click and scan totals with daily series per link
Check whether the account has unlocked the paid Core tier
When to use it: Useful when you want campaign links, QR codes for print or flyers, reusable UTM templates, digital business cards or simple landing pages created straight from a chat, with click and scan numbers read back in the same conversation.
Requirements: A Whooshly account and an agent token created in the app, supplied as WHOOSHLY_TOKEN for the stdio bridge or through the OAuth flow for the hosted endpoint. The npm bridge needs Node.js 18 or later. Reads and writes require the one-time Core unlock; the billing-status tool works on any account.

Before you install

The token grants access to your Whooshly account, so treat it as a secret. Most tools need a paid one-time Core unlock. Write tools create and edit links, QR codes, templates and pages on your account; the README says agents cannot delete anything or read leads' personal details, only counts. The stdio bridge forwards your messages and token to the hosted server.

Installation

In SourceWeft

Open Whooshly Mcp in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.whooshly%2Fwhooshly-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "whooshly": {
      "type": "http",
      "url": "https://app.whooshly.co/api/mcp"
    }
  }
}

README

Whooshly MCP

Give your AI assistant a campaign-link toolkit. Whooshly exposes a hosted Model Context Protocol server so Claude, ChatGPT, and any MCP client can create short links, dynamic QR codes, UTM templates, hosted vCard pages, and landing pages with lead capture – and read back real click/scan analytics – directly from a conversation.

"Shorten this launch URL, make a QR for the flyer, and save a UTM template for the paid-social campaign" → three tools, one message, links you actually own.

🔗 Short links on whooshly.co with live click tracking
🟧 Dynamic QR codes returned as scannable PNGs, right in the chat
🏷️ UTM templates you can reuse across campaigns
📇 Hosted vCard digital business cards
📊 Real analytics – exact click/scan totals and daily series per link
💸 Pay once. Unlock the core toolkit for a one-time price – no subscription. See pricing →

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.

1. Get an agent token

Every tool acts on your Whooshly account, so you need a token:

Sign in at app.whooshly.co
Open Agents → New token
Copy the token (shown once)

Reads and writes require the one-time Core unlock; get_billing_status works on any account so an agent can check before it acts.

2. Connect

Claude.ai / Claude (web, desktop, mobile) – by URL, no install

Add a Custom Connector pointing at the remote server. Claude runs the OAuth flow in-browser; approve it and the tools appear.

Settings → Connectors → Add custom connector → paste the URL.

ChatGPT – by URL

Add a connector / custom MCP server with the same URL:

Claude Code – one command

Then authenticate with /mcp inside Claude Code, or pass a token header:

bash

claude mcp add whooshly --transport http https://app.whooshly.co/api/mcp \  --header "Authorization: Bearer $WHOOSHLY_TOKEN"

claude mcp add whooshly --transport http https://app.whooshly.co/api/mcp \  --header "Authorization: Bearer $WHOOSHLY_TOKEN"

Claude Desktop (or any stdio client) – via this bridge

For clients that only speak stdio, use this package. Add it to your claude_desktop_config.json:

json

{  "mcpServers": {    "whooshly": {      "command": "npx",      "args": ["-y", "whooshly-mcp"],      "env": {        "WHOOSHLY_TOKEN": "your-agent-token"      }    }  }}

{  "mcpServers": {    "whooshly": {      "command": "npx",      "args": ["-y", "whooshly-mcp"],      "env": {        "WHOOSHLY_TOKEN": "your-agent-token"      }    }  }}

That's it – restart the client and the Whooshly tools are available.

Tools

Tool	What it does	Access
`get_billing_status`	Check whether the account has unlocked Core / Pro	any
`create_link`	Create a short link → id, slug, short URL	Core
`list_links`	List your links, newest first (cursor-paged)	Core
`get_link_stats`	Exact click/scan totals + daily series for a link	Core
`create_qr`	Create a dynamic QR code, returned as a scannable PNG	Core
`get_qr`	Re-fetch a saved QR code as a PNG	Core
`create_utm`	Save a reusable UTM template	Core
`list_utm`	List saved UTM templates	Core
`create_vcard`	Create a hosted digital business card (vCard) page	Core
`create_page`	Create a landing page on your subdomain from content blocks	Core
`update_page`	Edit a page's blocks, theme, or slug – never deletes	Core
`list_pages`	List your landing pages with lead counts	Core
`get_page`	One page's content, lead count & webhook delivery rollup	Core
`search`	Search your links by slug/destination (deep-research)	Core
`fetch`	Fetch full details of one link by id (deep-research)	Core

All read tools are annotated readOnlyHint; write tools can only create or edit – an agent can never delete anything, never read your leads' personal details (counts only), and never see or change a lead webhook. Every tool operates only on your own account (openWorldHint: false).

Example prompts

Once connected, try:

"Shorten https://example.com/2026-summer-launch with the slug summer26 and show me the QR code."
"Create a UTM template called paid-social with source instagram, medium cpc, campaign summer-launch."
"How many clicks did my summer26 link get this week?"
"Make a vCard for Jane Doe, Head of Growth at Acme, [email protected]."

Configuration

WHOOSHLY_API_TOKEN is accepted as an alias for WHOOSHLY_TOKEN.

How the bridge works

whooshly-mcp reads newline-delimited JSON-RPC from stdin, POSTs each message to the hosted server with your bearer token, and writes the correlated reply to stdout. It has zero npm dependencies (Node 18+ built-ins only), so it's small and easy to audit – the entire bridge is one file: bin/whooshly-mcp.mjs.

The heavy lifting – auth, rate limits, entitlement checks, QR rendering, analytics – all happens server-side on Whooshly. The bridge is a transport shim, nothing more.

License

MIT © Whooshly

Source: README.md at commit 2c2c8c6

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.1.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Env var	Default	Purpose
`WHOOSHLY_TOKEN`	–	Required for the stdio bridge. Your agent token.
`WHOOSHLY_MCP_URL`	`https://app.whooshly.co/api/mcp`	Override the endpoint (self-host / staging).

Whooshly Mcp

Overview

Installation

In SourceWeft

Use with an agent

Other MCP clients

README

Whooshly MCP

1. Get an agent token

2. Connect

Claude.ai / Claude (web, desktop, mobile) – by URL, no install

ChatGPT – by URL

Claude Code – one command

Claude Desktop (or any stdio client) – via this bridge

Tools

Example prompts

Configuration

How the bridge works

Links

License

Tools

Version history

Score