Skip to content
mcp/harbor

Linkbreakers MCP AGENTS.md changelog

com.linkbreakers/mcp

2 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • AGENTS.md +10 −9

    https://raw.githubusercontent.com/linkbreakers-com/agent-skills/HEAD/AGENTS.md 

    − | An assistant acting for a user in their workspace | MCP server `https://mcp.linkbreakers.com` (OAuth, no token handling) |− - Auth: `Authorization: Bearer <workspace token>`. Users create tokens at https://app.linkbreakers.com/workspace/dashboard/api-tokens. Secret keys (`WORKSPACE_TOKEN_KEY_TYPE_SECRET`) have full access and belong on servers only; publishable keys (`WORKSPACE_TOKEN_KEY_TYPE_PUBLISHABLE`) have limited access for browser use.− - **Media**: a PDF, image or MP4 video in the workspace's media library (`/v1/media`), counted against the plan's storage. An `EVENT_ACTION_OPEN_MEDIA` exit step opens one when a visitor scans (`POST /v1/links/open-media` creates such a link). Images of at most 3 MB can also be QR code logos and page theme covers, badges or footer logos.− brew install linkbreakers-com/tap/linkbreakers− export LINKBREAKERS_TOKEN=...− linkbreakers links create --destination https://example.com --wait-for-qrcode− linkbreakers raw GET "/v1/visitors?pageSize=50"− `raw METHOD PATH` reaches any endpoint. Docs: https://linkbreakers.com/cli and https://github.com/linkbreakers-com/linkbreakers-cli− - Product: `https://mcp.linkbreakers.com`, Streamable HTTP, OAuth 2.1. Claude Code: `claude mcp add --transport http linkbreakers https://mcp.linkbreakers.com`. Tool names are snake_case (`links_create`, `workflow_steps_create`, `workflow_steps_connect`, `workflow_steps_validate`, `visitors_list`, `domains_check`, ...).+ | An assistant acting for a user in their workspace | MCP server `https://mcp.linkbreakers.com` (OAuth, no token handling; API tokens are refused) |+ | Asked to create a link or QR code and there is no token yet | `npx -y linkbreakers-cli signup --email <the user's email>`: a workspace and a token in one command |+ - Auth: `Authorization: Bearer <workspace token>`. Workspace tokens work on the REST API, the SDKs and the CLI, not on the MCP server. Users with an account create tokens at https://app.linkbreakers.com/workspace/dashboard/api-tokens. With no account, `npx -y linkbreakers-cli signup --email <email>` creates a workspace and its token in one step (see CLI). Secret keys (`WORKSPACE_TOKEN_KEY_TYPE_SECRET`) have full access and belong on servers only; publishable keys (`WORKSPACE_TOKEN_KEY_TYPE_PUBLI+ - **Media**: a PDF, image or MP4 video in the workspace's media library (`/v1/media`), counted against the plan's storage. An `EVENT_ACTION_OPEN_MEDIA` exit step opens one when a visitor scans (`POST /v1/links/open-media` creates such a link). Images of at most 3 MB can also be QR code logos and page theme covers, badges or footer logos. A media item's file can be replaced in place (`POST /v1/media/{id}/replace-uploads`, `POST /v1/media/{id}/replace:import`), keeping its id so its uses follow; Q+ npx -y linkbreakers-cli signup --email you@example.com   # no account: a workspace and its token, saved+ npx -y linkbreakers-cli links create --destination https://example.com --wait-for-qrcode+ npx -y linkbreakers-cli visitors list --page-size 50+ npx -y linkbreakers-cli analytics-data get-top-links+ Every API operation is a command, `linkbreakers <service> <operation>`, generated from the OpenAPI spec; `--help` lists its flags and `--data` takes a JSON body. `signup` emails the person a link and a code to claim the workspace; the link and code go only to that inbox, never to you, so ask for the person's real address and tell them to open the email; unclaimed, the workspace is deleted after 24 hours. With an existing account, use `linkbreakers auth set-token --token <token>` or `LINKBREAKERS+ - Product: `https://mcp.linkbreakers.com`, Streamable HTTP, OAuth 2.1. It does not accept dashboard API tokens (it answers `API tokens are not accepted by the MCP server; connect with OAuth`); the only other credential it takes is the token from anonymous agent registration (https://linkbreakers.com/auth.md). Configure it with the plain URL and no `Authorization` header. Claude Code: `claude mcp add --transport http linkbreakers https://mcp.linkbreakers.com`. Tool names are snake_case (`links_cr

  • AGENTS.md +2 −1

    https://raw.githubusercontent.com/linkbreakers-com/agent-skills/HEAD/AGENTS.md 

    − 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, redirects) that turns an anonymous scan into an identified **visitor** carrying the attributes the business chose to collect. Leads leave through the REST API, webhooks, five SDKs, a CLI and an MCP server.+ 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, redirects, opening a PDF, image or video) that turns an anonymous scan into an identified **visitor** carrying the attributes the business chose to collect. Leads leave through the REST API, webhooks, five SDKs, a CLI and an MCP server.+ - **Media**: a PDF, image or MP4 video in the workspace's media library (`/v1/media`), counted against the plan's storage. An `EVENT_ACTION_OPEN_MEDIA` exit step opens one when a visitor scans (`POST /v1/links/open-media` creates such a link). Images of at most 3 MB can also be QR code logos and page theme covers, badges or footer logos.
Linkbreakers MCP MCP server