layervai/qurl-mcp

> **⚠️ Renamed from @layerv/qurl-mcp in v0.4.0.** The old package is deprecated and will not receive further updates. If you're using @layerv/qurl-mcp@0.3.x, swap the scope in your MCP client config — same binary, same API key, no other changes.
> A qURL MCP Server that supports both local stdio mode and remote HTTP mode for creating, managing, resolving, and sharing secure access links.
Overview
qURL MCP exposes qURL capabilities to MCP clients, GPTs, ChatGPT, and other remote integrations.
It currently supports:
- creating, reading, updating, and deleting qURLs
- resolving access tokens
- managing qURL tokens and sessions
- uploading text or file content and generating qURLs
- optionally serving LayerV public legal pages
- serving a configurable MP4 video playback page
Quick start: no account needed
Share an app running on your machine, or a URL, privately from Claude
Desktop, Claude Code, Cursor, Codex, or any local MCP client. You need no
account and no API key: with no QURL_API_KEY set, the server drives the
qURL CLI
installed on your machine, and the first publish creates this machine's
identity by itself.
**1. Install the qURL CLI** (macOS and Linux; Node.js 22.12 or later is
needed for the MCP server):
On Windows, download qurl.exe from the
latest release
and put its folder on PATH. The server finds qurl on PATH, and also in
~/.local/bin, /opt/homebrew/bin, and /usr/local/bin, which many MCP
clients leave off the PATH they give servers. If the CLI is missing, every
tool answers with this install command instead of failing.
**2. Add the server to your MCP client**, with no env block.
Claude Desktop (claude_desktop_config.json) and Cursor (~/.cursor/mcp.json):
Codex (~/.codex/config.toml):
Claude Code:
**3. Ask for what you want**, for example "share the app on localhost:3000
with my client". The agent publishes the app (it stays on your machine; the
CLI's background service keeps the share running), and gives you a
short-lived link for one person, or turns on access requests so people can
ask for access.
Tools without an account
| Tool | What it does | CLI command |
| ---------------------- | ---------------------------------------------------------------------------- | -------------------------------------------------------- |
| publish_crid | Publish a local app or URL privately and return its CRID | qurl publish [--allow-requests] [--access ] |
| share_by_crid | Make a short-lived access link for a CRID this machine published | qurl share [--ttl] [--session-duration] |
| list_crids | List this machine's published resources (read-only) | qurl list --status active |
| manage_crid_requests | List, approve by code, or deny access requests; list or remove approved people; turn requests on or off | qurl requests, qurl approve, qurl deny, qurl grants |
| manage_crid_access | Private access policy, invitations, and consumer grants | qurl access |
| set_crid_sharing | Stop, start, or restart sharing a local app | qurl stop, qurl start, qurl restart |
| delete_crid | Delete a resource permanently | qurl delete --yes |
The tools follow the same rules as the qURL agent skill
( ):
- Everything is published private. These tools have no option to publish
publicly.
- A pending access request is approved only with the six-digit code the
person gives you. No listing shows a code, and no tool approves by name:
anyone can type any name, and names come back as unverified data.
- An access link is a bearer secret for one recipient. A CRID grants nothing
by itself and is safe to share.
The server runs the CLI with an argument array (never a shell), with
JSON output, closed stdin, a timeout, and bounded output, and it does not
log what the CLI prints. The tools that need an account key (the qURL link,
token, session, and upload tools, and the qurl:// resources and prompts)
are not listed in this mode.
With an account key
Set QURL_API_KEY to a LayerV API key and the server uses the qURL API
directly, with the full tool set described in the feature map:
Remote HTTP server
The HTTP transport (qurl-mcp-http) serves remote agent runtimes. It is
account-based: every request carries the caller's qURL API key as a bearer
token, and it never runs a local CLI. See HTTP Authentication
and the LayerV MCP guide.
Private consumer access
Node.js 22.12 or later is required by the shared qURL SDK.
publish_crid creates a private URL resource with keys, invite_only,
email_capture, review, or contract access. manage_crid_access changes the
policy with its current version, sends invitations, lists grants, approves