Lynkarr Support
Contact us Sign in

Support / MCP and AI assistants

MCP tools: what an assistant can do

The nine MCP tools, the scope each one needs, and what each will refuse.

Checking the MCP connection

lynkarr_whoami needs no scope and answers with the account, the plan, the scopes the token holds and how much rate limit and quota is left. It is the first thing to try when something is refused, because it turns “that did not work” into “the token has no codes:write”.

Reading codes

lynkarr_list_qr_codes needs codes:read. It lists codes newest first with their current destination and scan count, and takes an optional name search so an account with two hundred codes does not have to be paged through.

lynkarr_get_qr_code needs codes:read and returns one code in full, given its id.

Making and changing codes

lynkarr_create_qr_code needs codes:write. Codes are dynamic unless you say otherwise, which is almost always what you want: a static code cannot be changed after printing, ever.

lynkarr_repoint_qr_code needs codes:write and is the one that earns the whole integration. It changes where an existing dynamic code goes. The pattern does not change, so everything already printed keeps working and starts going somewhere new.

lynkarr_archive_qr_code needs codes:write and stops a code resolving. Anything printed dies with it.

Repointing takes effect on the next scan. There is no cache to wait for.

Short links

lynkarr_list_short_links needs links:read. lynkarr_create_short_link needs links:write and takes an optional slug — leave it out and one is generated.

Analytics

lynkarr_get_scan_analytics needs analytics:read and reports scans for one code over a number of days, broken down by day, country and device.

It cannot tell you who scanned, on any plan, because that is not recorded anywhere. No cookies, no stored IP addresses, no cross-site identifier. The answer is how many, from where and on what — never who.

When something is refused

A refusal comes back as a tool error with the reason, not as a broken tool, so the assistant can explain it. The common ones: a missing scope, the plan's code allowance being full, the per-minute rate limit, and the monthly API quota. lynkarr_whoami tells you which of those you are against.

Connect an AI assistant with MCP →Connect Claude, ChatGPT, Copilot or Cursor over MCP →
Still stuck? Tell us what happened — we read every message. lynkarr.com