Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://app.whooshly.co/api/mcpThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http co.whooshly-whooshly-mcp https://app.whooshly.co/api/mcpRun in a terminal.
{ "mcpServers": { "co.whooshly-whooshly-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://app.whooshly.co/api/mcp" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
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 pages, and with lead capture – and read back real click/scan analytics – directly from a conversation.
Create short links, QR codes, UTM templates, vCards, and landing pages from your AI assistant.
"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.
whooshly.co with live click trackingThe 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.
Every tool acts on your Whooshly account, so you need a token:
Reads and writes require the one-time Core unlock; get_billing_status works on any account so an agent can check before it acts.
Add a Custom Connector pointing at the remote server. Claude runs the OAuth flow in-browser; approve it and the tools appear.
https://app.whooshly.co/api/mcp
Settings → Connectors → Add custom connector → paste the URL.
Add a connector / custom MCP server with the same URL:
https://app.whooshly.co/api/mcp
claude mcp add whooshly --transport http https://app.whooshly.co/api/mcp
Then authenticate with /mcp inside Claude Code, or pass a token header:
claude mcp add whooshly --transport http https://app.whooshly.co/api/mcp \
--header "Authorization: Bearer $WHOOSHLY_TOKEN"
For clients that only speak stdio, use this package. Add it to your claude_desktop_config.json:
{
"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.
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).
Once connected, try:
summer26 and show me the QR code."paid-social with source instagram, medium cpc, campaign summer-launch."summer26 link get this week?"WHOOSHLY_API_TOKEN is accepted as an alias for WHOOSHLY_TOKEN.
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.
https://app.whooshly.co/api/mcpMIT © Whooshly
© 2026 MCP Directory.
Create short links, QR codes, UTM templates, vCards, and landing pages from your AI assistant.
{ "mcpServers": { "co.whooshly-whooshly-mcp": { "url": "https://app.whooshly.co/api/mcp", "headers": {} } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: WHOOSHLY_TOKEN.
Whooshly is reached over HTTP.
Last checked 2026-11-08. Create short links, QR codes, UTM templates, vCards, and landing pages from your AI assistant.