Link infrastructure your agent can drive

Connect the MCP server and your assistant creates tracked links and QR codes, builds the journey behind them, and reads back who scanned what. REST and SDKs in five languages if you would rather call it yourself.

Describe what you want to build

Free plan. No card. MCP setup in one command.

MCP

One command to connect an assistant

5 SDKs

TypeScript, Python, Go, Java, Rust

Webhooks

Scan events pushed to your stack

Use cases

What teams like yours use it for

Let the agent build the journey

Describe the flow and it creates the link, the QR, the conditions and the destinations. The steps are real workflow objects, not a prompt that has to be re-run.

A tracked code per record

Generate one per customer, order or asset from your own code, each carrying its own analytics, without minting a new integration every time.

Read the scans back

Query who scanned what, where and when over the API, or have events pushed to a webhook as they happen.

White-label it

Serve links on your own domain so the infrastructure reads as yours, which matters if you are reselling it inside your own product.

FAQ

Questions we get asked

What does the MCP server actually let an assistant do?

Create and update links and QR codes, build and connect workflow steps, apply themes, and read analytics and visitor data. The same operations the REST API exposes.

Can I use it without MCP?

Yes. There is a REST API, SDKs for TypeScript, Python, Go, Java and Rust, a CLI, and Zapier and Make integrations.

Can I put it behind my own brand?

Yes. Bring your own domain and links resolve on it. Agencies and platforms run client-facing infrastructure this way.

How is it priced for programmatic use?

Self-serve plans cover normal volumes. For high-volume or reseller use, contact [email protected].