Snipzr

com.snipzrPublished by snipzr.comOfficial publisherv1.32.0Updated Oct 24, 2026

Short links with branded domains, cookie-less analytics and QR codes. Sign in with OAuth or a token

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Snipzr is a hosted MCP server that lets an assistant create, manage and measure branded short links, QR codes and campaign reports.

What you can do
Create single or batch short links on branded domains, and update or delete existing links with a confirmation gate for deletes. List and read links with text, domain and campaign filters. Read per-day click and scan statistics and campaign-level reports, with bots and automated traffic counted separately. Generate QR codes as PNG, JPEG or SVG with colors, captions and a logo, plus a signed download URL. Build UTM links following workspace conventions, list short domains and check plan usage.
When to use it
Useful when you want an assistant to produce and track short links and QR codes for campaigns, or to pull link and campaign performance without leaving the chat. It fits teams that already use Snipzr and want link work done conversationally.
Requirements
A remote Streamable HTTP endpoint; nothing to install. Sign-in via OAuth works on any plan, including Free. Clients without a browser need a Bearer token in the Authorization header, which requires a paid plan. Tokens are created in Snipzr settings and scoped to chosen workspaces and permissions.
Before you install
The connection can create, update and delete links in the workspaces you grant, and deletes are destructive. Links created by an agent count toward the same monthly allowance and API rate limit as manual work. Tokens are shown once and act as you or as a workspace, so scope them narrowly and revoke them in Settings if exposed. QR codes come with a short-lived signed download URL.

Installation

In SourceWeft

  1. Open Snipzr in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/com.snipzr%2Fmcp/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": {
    "snipzr": {
      "type": "http",
      "url": "https://mcp.snipzr.com/mcp"
    }
  }
}

README

Snipzr MCP Server

The official Snipzr MCP server. One hosted endpoint gives any MCP client thirteen tools to create, manage and measure short links: branded domains, batch creation, cookie-less analytics, campaign reports, UTM building and QR codes.

https://mcp.snipzr.com/mcp

There is nothing to install or run. The server is remote (Streamable HTTP), stateless and works on every Snipzr plan, Free included, when the client signs in with OAuth. Bearer tokens, for clients without a browser, need a paid plan. This repository is its public home: setup, the tool reference and the registry metadata. The server itself is part of the Snipzr platform, and its tools are thin adapters over the same handlers that serve the public REST API, so the two surfaces always behave identically.

Quick start

1. Connect with sign-in (recommended). Most clients need no token at all: point them at the server address and they open a Snipzr sign-in. The consent screen shows exactly which permissions the application gets and which of your workspaces it may act in; untick anything you do not want, and disconnect it later from Settings.

Claude Code, two commands:

bash
claude mcp add --transport http snipzr https://mcp.snipzr.com/mcpclaude mcp login snipzr

Claude on the web, desktop and mobile: open Settings, then Connectors, then Add custom connector, enter the server address and select Connect. ChatGPT connects the same way in developer mode. Smithery, Glama and other directories connect through the same sign-in.

2. Or use a token. In Settings, create a token and copy the secret (it is shown exactly once):

  • User API tokens act as you. Pick the workspaces the token may act in and what it may do in each one.
  • Workspace API tokens belong to one workspace and act as that workspace. The right choice for a shared team assistant or a client without a browser.

Cursor, VS Code and any other MCP client take the generic remote config:

json
{  "mcpServers": {    "snipzr": {      "url": "https://mcp.snipzr.com/mcp",      "headers": { "Authorization": "Bearer YOUR_TOKEN" }    }  }}

A client that only speaks stdio can bridge with npx mcp-remote https://mcp.snipzr.com/mcp --header "Authorization: Bearer YOUR_TOKEN".

3. Confirm it worked. Ask your assistant to list the Snipzr tools. Thirteen names starting with snipzr_ means you are connected.

The thirteen tools

ToolWhat it doesScope
snipzr_create_linkCreate one short link: destination, optional domain, back-half, titlelinks:write
snipzr_create_links_batchCreate up to 100 short links in one calllinks:write
snipzr_list_linksList links with text, domain and campaign filterslinks:read
snipzr_get_linkRead one link by its back-halflinks:read
snipzr_update_linkChange a destination or titlelinks:write
snipzr_delete_linkDelete a link, with a confirmation gatelinks:write
snipzr_get_link_statsPer-day clicks and scans, with bots, AI assistants and suspected automated traffic counted separatelystats:read
snipzr_get_campaign_reportClicks rolled up by campaignstats:read
snipzr_get_usagePlan, remaining allowance and reset dateusage:read
snipzr_list_domainsYour short domains and their statusdomains:read
snipzr_get_qr_codeA scannable QR code (PNG, JPEG or SVG) with colors, a caption and a logo, plus a signed download URLlinks:read
snipzr_build_utm_linkCompose a UTM link that follows your workspace's conventionslinks:read
snipzr_list_workspacesThe workspaces this connection can act in, with the ids to pass as workspaceIdany

Every tool carries read-only or destructive annotations, so well-behaved clients ask before a delete and never before a read, and every tool publishes an output schema and returns structured content beside the text, so agents read fields instead of parsing prose.

Access model

  • Scopes narrow a token to just what it needs: links:read, links:write, stats:read, usage:read, domains:read. A call outside the token's scopes is refused with a message that names the missing scope.
  • Connections act in the workspaces you chose. A sign-in connection reaches exactly the workspaces you ticked on the consent screen; a user token reaches the ones picked when it was created. Personal workspace by default. To work in another granted workspace, the assistant passes its id as the workspaceId argument of any tool (snipzr_list_workspaces lists them). Access follows your live membership there, checked on every call: leave a workspace and the token loses it instantly; get re-added and it resumes at your new role.
  • Workspace tokens are their one workspace and refuse any other. They are not tied to a person, so people can come and go while automations keep working.
  • Refusals carry stable codes (SCOPE_REQUIRED, NOT_GRANTED, GRANT_INACTIVE, GRANT_REDUCED, PLAN_REQUIRED) so an agent can explain and self-correct.

Good to know

  • Links an agent creates count toward the same monthly allowance as links you create by hand, and requests share the plan's API rate limit. snipzr_get_usage reports both before bulk work.
  • QR codes come back as an inline image plus a short-lived signed download URL, so an agent can save the file without pushing image bytes through the model.
  • Revoking a token or disconnecting an application in Settings cuts the client off immediately, and a disconnected application cannot quietly reconnect: it has to ask you again.
  • The server never logs your destinations, and analytics stay cookie-less.

Links

Support

Questions and problem reports are welcome in this repository's issues, or at [email protected]. Please never post a token secret; if one leaks, revoke or roll it in Settings first.

Source: README.md at commit b46fd2e

Tools

0
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

2
  1. v1.32.0LatestOct 10, 2026
  2. v1.11.3Sep 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