Deleting the qURL removes the resource and every token beneath it, irreversibly; revoking a token stops one recipient while siblings keep working; terminating sessions ends access that is already open without changing whether new redemptions are allowed. One caution before wiring uploads into an autonomous agent: the local-file upload can read any file the server process can read, and the vendor's own guidance is to keep it away from untrusted prompts and run it under an account whose readable files are already limited to what you mean to share.
A qURL client for creating access links that gate a target URL behind a policy and an expiry, redeeming them for a time- and IP-bound access grant, and managing the resources, tokens and live sessions underneath. It runs as a local subprocess for desktop clients, or as an authenticated remote server for agent runtimes.
- create_qurl mints a policy-bound expiring link with optional IP, geo, user-agent and AI-agent filters, an expiry, a session duration, a maximum session count, a one-time-use flag and an optional custom domain.
- resolve_qurl redeems an access token to reveal the underlying URL and obtain a time- and IP-bound grant, which is how an agent fetches a resource it was handed a link to.
- Discovery: list_qurls filtered by status, date range and full-text search across descriptions and target URLs, and get_qurl by resource ID or display ID, the latter resolved to its parent automatically.
- Lifecycle edits: extend_qurl as the relative-time shortcut, update_qurl for expiry, tags, description, custom domain and proxy host-header behaviour, and delete_qurl, which revokes the link and every token under it irreversibly.
- Token-level control separate from the resource: mint_link issues an additional access link on an existing resource, update_qurl_token changes one token's expiry, label, policy, session cap or duration, and revoke_qurl_token stops one recipient while its siblings keep working.
- Live sessions: list_qurl_sessions shows who currently holds access, and terminate_qurl_sessions ends one session or all of them for a resource.
- batch_create_qurls creates up to 100 qURLs in one request, returning per-item results with succeeded and failed counts.
- With a connector configured, upload_text_qurl and upload_file_data_qurl put content behind a fresh qURL in one step, and upload_file_qurl does the same for a local file — that one only in local mode.
- Two resources the client can read directly: the current qURL list, and current quota and usage.
A qURL account and its API key in QURL_API_KEY, scoped for the operations you intend — reading, writing, resolving. Uploads additionally need a connector URL configured, and emailing a link out needs SMTP settings. Token-level operations need both the parent resource ID and the token's display ID.
One command plus a key — npx @layervai/qurl-mcp, then supply credentials