qURL

Name: qURL
Author: layervai

by layervaiversion 0.9.0i★ –iRuns on your computer

Registry nameio.github.layervai/qurl-mcp

Install

Overview

Description from the maker (original English)

Mint, resolve, audit, and rotate scope-limited expiring access links (qURLs) for AI agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiEarly↓ 574/wk · ★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: QURL_API_KEY, QURL_SMTP_USERNAME, QURL_SMTP_PASSWORD

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: QURL_API_KEY, QURL_API_URL, QURL_CONNECTOR_URL, QURL_LINK_HOSTS, QURL_MCP_CONFIG, MCP_MAX_UPLOAD_FILE_DATA_BYTES, QURL_SMTP_HOST, QURL_SMTP_PORT, QURL_SMTP_SECURE, QURL_SMTP_USERNAME, QURL_SMTP_PASSWORD, QURL_SMTP_FROM_EMAIL, QURL_SMTP_FROM_NAME, QURL_SMTP_ALLOWED_RECIPIENTS, QURL_SMTP_ALLOWED_RECIPIENT_DOMAINS, QURL_SMTP_MAX_RECIPIENTS_PER_MESSAGE, QURL_SMTP_MAX_RECIPIENTS_PER_HOUR, QURL_MCP_FEEDBACK

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "qurl": {
      "command": "npx",
      "args": [
        "-y",
        "@layervai/qurl-mcp"
      ],
      "env": {
        "QURL_API_KEY": "your-value",
        "QURL_API_URL": "your-value",
        "QURL_CONNECTOR_URL": "your-value",
        "QURL_LINK_HOSTS": "your-value",
        "QURL_MCP_CONFIG": "your-value",
        "MCP_MAX_UPLOAD_FILE_DATA_BYTES": "your-value",
        "QURL_SMTP_HOST": "your-value",
        "QURL_SMTP_PORT": "your-value",
        "QURL_SMTP_SECURE": "your-value",
        "QURL_SMTP_USERNAME": "your-value",
        "QURL_SMTP_PASSWORD": "your-value",
        "QURL_SMTP_FROM_EMAIL": "your-value",
        "QURL_SMTP_FROM_NAME": "your-value",
        "QURL_SMTP_ALLOWED_RECIPIENTS": "your-value",
        "QURL_SMTP_ALLOWED_RECIPIENT_DOMAINS": "your-value",
        "QURL_SMTP_MAX_RECIPIENTS_PER_MESSAGE": "your-value",
        "QURL_SMTP_MAX_RECIPIENTS_PER_HOUR": "your-value",
        "QURL_MCP_FEEDBACK": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add qurl --env QURL_API_KEY=your-value --env QURL_API_URL=your-value --env QURL_CONNECTOR_URL=your-value --env QURL_LINK_HOSTS=your-value --env QURL_MCP_CONFIG=your-value --env MCP_MAX_UPLOAD_FILE_DATA_BYTES=your-value --env QURL_SMTP_HOST=your-value --env QURL_SMTP_PORT=your-value --env QURL_SMTP_SECURE=your-value --env QURL_SMTP_USERNAME=your-value --env QURL_SMTP_PASSWORD=your-value --env QURL_SMTP_FROM_EMAIL=your-value --env QURL_SMTP_FROM_NAME=your-value --env QURL_SMTP_ALLOWED_RECIPIENTS=your-value --env QURL_SMTP_ALLOWED_RECIPIENT_DOMAINS=your-value --env QURL_SMTP_MAX_RECIPIENTS_PER_MESSAGE=your-value --env QURL_SMTP_MAX_RECIPIENTS_PER_HOUR=your-value --env QURL_MCP_FEEDBACK=your-value -- npx -y @layervai/qurl-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "qurl": {
      "command": "npx",
      "args": [
        "-y",
        "@layervai/qurl-mcp"
      ],
      "env": {
        "QURL_API_KEY": "your-value",
        "QURL_API_URL": "your-value",
        "QURL_CONNECTOR_URL": "your-value",
        "QURL_LINK_HOSTS": "your-value",
        "QURL_MCP_CONFIG": "your-value",
        "MCP_MAX_UPLOAD_FILE_DATA_BYTES": "your-value",
        "QURL_SMTP_HOST": "your-value",
        "QURL_SMTP_PORT": "your-value",
        "QURL_SMTP_SECURE": "your-value",
        "QURL_SMTP_USERNAME": "your-value",
        "QURL_SMTP_PASSWORD": "your-value",
        "QURL_SMTP_FROM_EMAIL": "your-value",
        "QURL_SMTP_FROM_NAME": "your-value",
        "QURL_SMTP_ALLOWED_RECIPIENTS": "your-value",
        "QURL_SMTP_ALLOWED_RECIPIENT_DOMAINS": "your-value",
        "QURL_SMTP_MAX_RECIPIENTS_PER_MESSAGE": "your-value",
        "QURL_SMTP_MAX_RECIPIENTS_PER_HOUR": "your-value",
        "QURL_MCP_FEEDBACK": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "qurl": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@layervai/qurl-mcp"
      ],
      "env": {
        "QURL_API_KEY": "your-value",
        "QURL_API_URL": "your-value",
        "QURL_CONNECTOR_URL": "your-value",
        "QURL_LINK_HOSTS": "your-value",
        "QURL_MCP_CONFIG": "your-value",
        "MCP_MAX_UPLOAD_FILE_DATA_BYTES": "your-value",
        "QURL_SMTP_HOST": "your-value",
        "QURL_SMTP_PORT": "your-value",
        "QURL_SMTP_SECURE": "your-value",
        "QURL_SMTP_USERNAME": "your-value",
        "QURL_SMTP_PASSWORD": "your-value",
        "QURL_SMTP_FROM_EMAIL": "your-value",
        "QURL_SMTP_FROM_NAME": "your-value",
        "QURL_SMTP_ALLOWED_RECIPIENTS": "your-value",
        "QURL_SMTP_ALLOWED_RECIPIENT_DOMAINS": "your-value",
        "QURL_SMTP_MAX_RECIPIENTS_PER_MESSAGE": "your-value",
        "QURL_SMTP_MAX_RECIPIENTS_PER_HOUR": "your-value",
        "QURL_MCP_FEEDBACK": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

QURL_API_KEY secret env
Optional. Without it, the tools run through the local qURL CLI (qurl), which needs no account. With it, the tools use the qURL API: a key with qurl:read, qurl:write, and/or qurl:resolve scopes from h…
QURL_API_URL env
qURL API base URL. Defaults to https://api.layerv.ai. Override only for testing against a non-production qURL backend.
QURL_CONNECTOR_URL env
Connector base URL used by local-file, file-data, and text-to-PDF upload tools before minting a qURL.
QURL_LINK_HOSTS env
Optional comma-separated exact hostnames or IPs for uploaded-file links. No schemes, ports, or wildcards. Blank values retain any file-configured policy.
QURL_MCP_CONFIG env
Optional path to a shared qURL MCP config file. Both stdio and HTTP modes can read SMTP, connector, and default API settings from this file.
MCP_MAX_UPLOAD_FILE_DATA_BYTES env
Maximum decoded/local upload size. Accepts bytes or units such as 10mb; capped at 100mb.
QURL_SMTP_HOST env
SMTP hostname for optional qURL link delivery.
QURL_SMTP_PORT env
SMTP port for optional qURL link delivery.
QURL_SMTP_SECURE env
Whether SMTP uses an implicit TLS connection (true/false).
QURL_SMTP_USERNAME secret env
SMTP authentication username.
QURL_SMTP_PASSWORD secret env
SMTP authentication password or app-specific credential.
QURL_SMTP_FROM_EMAIL env
Validated sender email address for qURL delivery.
QURL_SMTP_FROM_NAME env
Optional sender display name for qURL delivery.
QURL_SMTP_ALLOWED_RECIPIENTS env
Optional comma-separated exact recipient allowlist.
QURL_SMTP_ALLOWED_RECIPIENT_DOMAINS env
Optional comma-separated recipient-domain allowlist.
QURL_SMTP_MAX_RECIPIENTS_PER_MESSAGE env
Maximum recipients in one delivery request (default 10).
QURL_SMTP_MAX_RECIPIENTS_PER_HOUR env
Maximum attempted recipients per qURL key per fixed hourly window (default 100).
QURL_MCP_FEEDBACK env
Set to off to hide and disable outbound LayerV product feedback. Default on. Feedback is sent only by an explicit submit_feedback tool call.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account layervai, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 18486 servers in this category
Published to the registry more recently than 84% of the other 18486 servers in this category
Basic checks equal to or better than 100% of the other 18486 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is qURL safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: QURL_API_KEY, QURL_SMTP_USERNAME, QURL_SMTP_PASSWORD

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.9.0) reached the registry 8 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Compose Preview Catalogs

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app

Install

Compose Preview Catalogs

Browse, inspect and render Jetpack Compose Material 3 and Wear component catalogs.

by yschimkeVery newUpdated today

Runs in the cloud

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

qURL MCP server for temporary access links

Give an AI agent tools to share localhost web apps, private APIs, and selected files through expiring qURL™ by LayerV access links. This repository implements the Model Context Protocol server for that workflow. The @layervai/qurl-mcp package runs as a local stdio server backed by the qURL CLI or API, or as an authenticated remote HTTP server backed by the API.

Start with the no-account local quickstart or account-backed client configuration, then choose the tools for your task. In local mode, publish_crid runs the installed CLI to publish an app that is already running; share_by_crid issues its access link. Creating a link alone does not publish an app or restrict an existing public URL. Uploads require the account-backed tool set and use a separate connector lifecycle; see upload tools for their supported options and limits.

Local app sharing · File sharing · Sharing questions · Private links

⚠️ 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.

Let an AI agent share a localhost preview

Use this workflow when an agent needs to give a reviewer access to a development preview or internal API. A tool that creates a link does not start the app on your laptop.

Keep the local app running. Configure a local stdio MCP client using the no-account quickstart, with the qURL CLI installed on the same host and no QURL_API_KEY set.
Ask the agent to call publish_crid with app_name (a short public name, without secrets or recipient details) and the app's root loopback URL, such as http://127.0.0.1:3000, and save the returned CRID. Alternatively, publish it directly with the CLI. Local tools use that machine's device identity; a CRID does not grant another device authority over the resource.
Ask the agent to call share_by_crid with the published CRID and a requested lifetime. The following is a tool argument object, not a complete MCP message:

"crid": "REPLACE_WITH_PUBLISHED_CRID", "ttl": "5m" }

Share the full returned link through your intended private channel and report the expiry returned by the service. Do not assume the requested TTL was granted unchanged. Keep the publishing host and app available.

Check that your installed release exposes these tools. In account-backed mode, share_by_crid instead uses the API credential and requires qurl:resolve and resource authorization. For resources already managed through the API, see mint_link and the other link-management tools. Tool availability and resource identifiers matter; an uploaded-file identifier cannot be substituted into the same workflow.

Let an AI agent share a PDF or image

For example, give a reviewer a short-lived link to a selected PDF report. Use account-backed stdio mode (QURL_API_KEY set) or authenticated HTTP mode, then configure the upload Connector under configuration files. Upload tools are not listed in no-account local mode. Choose the tool for the transport:

File location	Tool	Important requirement
A PDF or supported raster image on the local MCP server host	`upload_file_qurl`	Available in stdio mode; the host process must be allowed to read the selected file.
PDF or image bytes supplied to an HTTP or stdio MCP client	`upload_file_data_qurl`	Supply the supported file as base64 data with the correct filename and media type.
A file already stored by an upload tool	`mint_uploaded_file_link`	Reuse its resource ID to mint a fresh link without another upload.
Text to share as a generated PDF	`upload_text_qurl`	Uses the configured upload service, rather than publishing a local app.

A stdio tool argument example:

"file_path": "/absolute/path/to/review.pdf", "expires_in": "5m", "one_time_use": true }

Pass these arguments to upload_file_qurl only for a file the user selected. The tool uploads to the configured file service and returns a new access link. Use the confirmed expiry in its response. Opening a single-use link to test it can consume it before the recipient opens it.

Upload links cannot currently be revoked through this MCP server, and mint_link cannot create another link for an uploaded file. See upload tools for the supported formats, size limits, response fields, and cleanup limitations.

Choosing what an agent should share

Should the agent share an app or a deployed preview?

If the reviewer needs the current localhost app, keep it running and use the local CLI-backed tools to publish the resource and issue its link. An existing ngrok endpoint, Cloudflare application, or Vercel preview is another possible handoff, but its access controls and availability come from that separately configured service. This server exposes qURL operations; it does not create those other deployments. See the app-sharing comparison when choosing the workflow. Share the confirmed expiry and preserve the app's login requirements.

Should the agent upload the result or link to a running file service?

A selected PDF or image can use this server's account-backed upload tools. A hosted Google Drive document instead uses Drive's sharing permissions; an S3 object can use a presigned download URL. Those storage workflows are distinct from publishing a local file server, which must remain available. Choose based on where the result should live and which service the agent is authorized to use. This server's upload identifiers and revocation limits still apply; a file path, uploaded-file identifier, and local-service CRID are not interchangeable.

MCP sharing questions

Is this a public tunnel to my localhost app?

In no-account stdio mode, this server invokes the local CLI to publish and manage an already running app. API-backed and remote HTTP modes use their configured resources; a remote server cannot publish an app on your laptop through its own localhost address. Use the localhost-sharing comparison when choosing between resource access links and a public endpoint workflow.

Does every AI client support the same tools?

No. Configure the client's supported transport and check the installed server's tool list. A remote HTTP server cannot use upload_file_qurl to read a file from the client's laptop; use the file-data tool for a supported attachment.

Can I use an app link and an uploaded-file link interchangeably?

No. App resource management and uploaded-file link minting use different lifecycles. Follow the tool that issued the link, including its revocation limits. Your local app's own login continues to apply when the link opens it.

Overview

The server exposes qURL operations as MCP tools for clients that support the configured transport. See the LayerV MCP guide for product setup and the tables below for the capabilities in this source version.

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):

(umask 022 && mkdir -p "$HOME/.local/bin" "$HOME/.local/state") && chmod go-w "$HOME/.local" "$HOME/.local/bin" "$HOME/.local/state" && curl -fsSL --proto '=https' https://raw.githubusercontent.com/layervai/qurl-integrations/main/scripts/install.sh | INSTALL_DIR="$HOME/.local/bin" sh

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):

"mcpServers": { "qurl": { "command": "npx", "args": ["-y", "@layervai/qurl-mcp"] } } }

Codex (~/.codex/config.toml):

[mcp_servers.qurl]

command = "npx" args = ["-y", "@layervai/qurl-mcp"]

Claude Code:

claude mcp add qurl -- npx -y @layervai/qurl-mcp

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 (https://layerv.ai/skills/qurl/SKILL.md):

Everything is published private.

Only the beginning is shown; read the rest in the repo

qURL

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Compose Preview Catalogs

README from the maker

qURL MCP server for temporary access links

Let an AI agent share a localhost preview

Let an AI agent share a PDF or image

Choosing what an agent should share

Should the agent share an app or a deployed preview?

Should the agent upload the result or link to a running file service?

MCP sharing questions

Is this a public tunnel to my localhost app?

Does every AI client support the same tools?

Can I use an app link and an uploaded-file link interchangeably?

Overview

Quick start: no account needed

Tools without an account