Connect Your AI With MCP

Snipzr runs a remote MCP server at https://mcp.snipzr.com/mcp. Once your client is connected, your assistant can create links on your domain, list and update them, read cookie-less stats and campaign reports, check your quota, build UTM links and render QR codes, asking you first before anything destructive. There is nothing to install: it is one hosted endpoint, available on every paid plan.

Get a token

1. Open Settings and find User API tokens.
2. Select Create token and name it after the client, for example Claude Code. Pick the workspaces it may act in and untick any scope the client should not have there. A read-only assistant needs nothing beyond the read scopes.
3. Copy the secret. It is shown exactly once; if you lose it, roll the token for a fresh one.

A workspace token (from the Workspace API tokens card) works too: it acts as that one workspace and is the right choice for a shared team assistant.

One token per client is the healthy habit: when a laptop or a client goes away, you revoke just that token and everything else keeps working.

Connect your client

Claude Code, one command, with your token in place of YOUR_TOKEN:

claude mcp add --transport http snipzr https://mcp.snipzr.com/mcp --header "Authorization: Bearer YOUR_TOKEN"

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

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

In Cursor this lives in .cursor/mcp.json; in VS Code, in your mcp.json, where GitHub Copilot's agent mode picks it up. A client that only speaks stdio can bridge with npx mcp-remote https://mcp.snipzr.com/mcp.

To confirm it worked, ask your assistant to list the Snipzr tools. Twelve names starting with snipzr_ means you are connected.

The twelve tools

Tool	What it does	Scope
snipzr_create_link	Create one short link: destination, optional domain, back-half, title	links:write
snipzr_create_links_batch	Create up to 100 links in one call	links:write
snipzr_list_links	List links with text, domain and campaign filters	links:read
snipzr_get_link	Read one link by its back-half	links:read
snipzr_update_link	Change a destination or title	links:write
snipzr_delete_link	Delete a link, with a confirmation gate	links:write
snipzr_get_link_stats	Per-day clicks and scans, bots counted separately	stats:read
snipzr_get_campaign_report	Clicks rolled up by campaign	stats:read
snipzr_get_usage	Plan, remaining allowance and reset date	usage:read
snipzr_list_domains	Your short domains and their status	domains:read
snipzr_get_qr_code	A scannable PNG QR code for an existing link	links:read
snipzr_build_utm_link	Compose a UTM link that follows your conventions	links:read

Every tool carries read-only or destructive annotations, so clients ask before a delete and never before a read. Links an agent creates count toward the same monthly allowance as links you create by hand, and the server tells the agent plainly when the allowance runs out.

Good to know

• The server acts only within the scopes on the token; everything else is refused with a message that names the missing scope.
• A user token acts in your personal workspace by default. To work in another workspace on the token, the assistant passes that workspace's id as the workspaceId argument of any tool; the server checks your live membership there on every call, so leaving a workspace cuts the token's access to it instantly.
• Revoking a token in Settings cuts the client off immediately.
• The server never logs your destinations, and analytics stay cookie-less.
• The full setup page with per-client details lives at snipzr.com/integrations/mcp.