Native qURL™ tools in any MCP client.
Let MCP-compatible agents create, resolve, list, and manage qURLs without custom integration code.
The usual way to do this is leaky
Reaching a private resource from MCP usually means one of these workarounds — each of which leaves something standing that shouldn’t be.
- Hand-writing REST calls in every agent to mint and resolve links
- Long-lived API keys baked into agent configs
- Custom glue code to list, revoke, and refresh access
Verify the requester, then open one private route
Requester
A MCP user or agent asks for access to a private resource.
LayerV
Identity and policy are verified before anything becomes reachable.
Private resource
Connected to LayerV with no public inbound path of its own.
Temporary route
A single-use, identity-bound qURL™ opens for the approved requester, then expires.
Real code you can run today
{
"mcpServers": {
"qurl": {
"command": "npx",
"args": ["@layervai/qurl-mcp"],
"env": { "QURL_API_KEY": "lv_live_xxx" }
}
}
}Full, open-source examples live on GitHub →
From zero to first access
- 1
Get an API key
Create a key with the qurl:read, qurl:write, and qurl:resolve scopes.
- 2
Add the server to your MCP client
Drop `npx @layervai/qurl-mcp` into your mcpServers config — Claude Desktop, Claude Code, Cursor, or any MCP client.
- 3
Use the tools natively
The agent calls create_qurl, resolve_qurl, list_qurls, and more — no custom integration code.
- 4
Resolve to reach the target
resolve_qurl redeems a single-use token and opens network access for a short grant.
Works today
- Published MCP server: npx @layervai/qurl-mcp
- 13 native tools — create, resolve, list, update, and revoke qURLs
- MCP resources for links and quota (qurl://links, qurl://usage)
- Listed in the Smithery and Glama MCP directories
- Works in Claude Desktop, Claude Code, Cursor, and any MCP client
Install the MCP server
New to LayerV? How it works · OpenNHP · API docs