Linkbreakers MCP
com.linkbreakersPublished by linkbreakers.comOfficial publisherv1.194.1Updated Nov 7, 2026
QR-driven customer-journey platform for tracked QR codes, short links, and analytics.
Overview
Connects an assistant to a Linkbreakers workspace to create tracked QR codes and short links, build lead-capture workflows, and read visitor and lead data.
- What you can do
- Create tracked QR codes and short links, including ones that open a PDF, image or video, and change destinations later
- Build lead-capture workflows with forms, conditions, password gates, multi-link pages and contact cards
- List, filter, sort and export captured visitors, events and funnels
- Push scans and leads to webhooks and tie a scan to a later signup or purchase
- Manage branded custom domains and debug their DNS and certificates
- When to use it
- Useful when you run QR codes or short links for offline or print campaigns and want an assistant to create links, adjust their destinations, build capture flows, or pull and export the resulting leads and analytics from your workspace.
- Requirements
- Remote endpoint at mcp.linkbreakers.com, or the npm package linkbreakers-mcp run with npx over stdio. Authentication is required: OAuth sign-in in the browser, or a workspace API token supplied as LINKBREAKERS_API_TOKEN or an Authorization bearer header for clients without OAuth. Network access to Linkbreakers services.
Installation
In SourceWeft
- Open Linkbreakers 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/com.linkbreakers%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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"linkbreakers": {
"type": "http",
"url": "https://mcp.linkbreakers.com/"
}
}
}README
Linkbreakers agent skills
The single source of truth for everything Linkbreakers exposes to AI agents: skills, agent instructions, plugin manifests and a machine-readable discovery index.
Linkbreakers is lead capture infrastructure for the physical world. Every QR code or link runs a workflow (forms, conditions, password gates, multi-link pages, contact cards) that turns an anonymous scan into an identified visitor.
Install the skills
Any agent supported by the skills CLI (Claude Code, Cursor, Codex, GitHub Copilot, Windsurf, Gemini, Cline and more):
Claude Code plugin
Bundles the skills and the hosted Linkbreakers MCP servers:
Other Agent Plugins clients
This repository is an Agent Plugin: plugin.json, skills/ and mcp.json at the root.
Skills
Linkbreakers for agents
discovery.json
discovery.json is the machine-readable index of all of the above, validated by schema/discovery.schema.json. linkbreakers.com reads it at runtime from:
Its skills[] array is generated from the skills/ folders:
Contributing
Add a folder under skills/ with a SKILL.md whose frontmatter has name (same as the folder) and description, regenerate discovery.json, and open a pull request. Ground every step in the real API: check the OpenAPI spec rather than guessing.
License
Source: README.md at commit a812c09
Tools
0Version history
54- v1.194.1LatestNov 7, 2026
- v1.193.2Nov 6, 2026
- v1.193.1Nov 5, 2026
- v1.193.0Nov 5, 2026
- v1.192.1Nov 5, 2026
- v1.190.0Nov 4, 2026
- v1.188.5Nov 3, 2026
- v1.188.2Nov 2, 2026
- v1.188.1Nov 1, 2026
- v1.187.1Nov 1, 2026
- v1.187.0Oct 31, 2026
- v1.186.2Oct 30, 2026
- v1.186.1Oct 29, 2026
- v1.184.0Oct 25, 2026
- v1.183.3Oct 21, 2026
- v1.183.1Oct 20, 2026
- v1.183.0Oct 18, 2026
- v1.182.0Oct 18, 2026
- v1.180.0Oct 17, 2026
- v1.178.0Oct 16, 2026
- v1.176.4Oct 14, 2026
- v1.176.3Oct 13, 2026
- v1.176.2Oct 12, 2026
- v1.176.0Oct 11, 2026
- v1.171.0Oct 11, 2026
- v1.170.0Oct 11, 2026
- v1.164.1Oct 10, 2026
- v1.150.0Oct 10, 2026
- v1.140.0Oct 10, 2026
- v1.138.6Oct 9, 2026
- v1.138.5Oct 8, 2026
- v1.138.3Oct 6, 2026
- v1.138.2Oct 6, 2026
- v1.138.0Oct 5, 2026
- v1.137.2Oct 5, 2026
- v1.137.1Oct 4, 2026
- v1.136.0Oct 4, 2026
- v1.135.1Oct 3, 2026
- v1.134.1Oct 3, 2026
- v1.131.11Oct 2, 2026
- v1.131.9Oct 2, 2026
- v1.131.8Oct 2, 2026
- v1.129.3Oct 1, 2026
- v1.128.3Oct 1, 2026
- v1.128.2Oct 1, 2026
- v1.128.1Sep 30, 2026
- v1.128.0Sep 30, 2026
- v1.127.0Sep 23, 2026
- v1.125.5Sep 21, 2026
- v1.125.2Sep 20, 2026
- v1.125.1Sep 20, 2026
- v1.124.0Sep 18, 2026
- v1.123.2Sep 16, 2026
- v1.123.1Sep 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