Built for Humans and AI
Give your agents access to URnetwork. Whole internet encryption with the same identity and privacy guarantees, no exceptions.
Connect with MCP (recommended route)
URagent https://mcp.bringyour.com
claude mcp add --transport http urnetwork https://mcp.bringyour.com
{
"mcpServers": {
"urnetwork": { "url": "https://mcp.bringyour.com" }
}
}code --add-mcp '{"name":"urnetwork","type":"http","url":"https://mcp.bringyour.com"}'codex mcp add urnetwork --url https://mcp.bringyour.com
{
"mcpServers": {
"urnetwork": { "type": "streamableHttp", "url": "https://mcp.bringyour.com" }
}
}Settings → Connectors → Add custom connector → https://mcp.bringyour.com
Settings → Developer mode → + → MCP server URL: https://mcp.bringyour.com
openclaw mcp add urnetwork --url https://mcp.bringyour.com --transport streamable-http --auth oauth
hermes mcp add urnetwork --url https://mcp.bringyour.com --auth oauth
{
"mcp": {
"urnetwork": { "type": "remote", "url": "https://mcp.bringyour.com", "enabled": true }
}
}{
"mcpServers": {
"urnetwork": { "serverUrl": "https://mcp.bringyour.com" }
}
}Settings → Connections → MCP servers → Add a custom MCP → Streamable HTTP → https://mcp.bringyour.com
Settings → Connectors → Add connector → https://mcp.bringyour.com
{
"context_servers": {
"urnetwork": { "url": "https://mcp.bringyour.com" }
}
}droid mcp add urnetwork https://mcp.bringyour.com --type http
{
"mcpServers": {
"urnetwork": { "url": "https://mcp.bringyour.com" }
}
}{
"mcpServers": {
"urnetwork": { "url": "https://mcp.bringyour.com" }
}
}qwen mcp add --transport http urnetwork https://mcp.bringyour.com
gemini mcp add --transport http urnetwork https://mcp.bringyour.com
grok.com → Connectors → New Connector → Custom → https://mcp.bringyour.com
kimi → /mcp-config → "add urnetwork https://mcp.bringyour.com"
OAuth: run /mcp in a session, pick urnetwork, and finish the browser sign-in.
.cursor/mcp.json (or ~/.cursor/mcp.json). Authenticate under Settings → MCP; the browser consent opens on connect.
OAuth: on first start VS Code shows a trust prompt, then opens the browser sign-in (Copilot agent mode).
OAuth: codex mcp login urnetwork opens the browser sign-in.
MCP Servers → Remote Servers → Add (or cline_mcp_settings.json); recent builds run the browser sign-in when the server asks.
Every plan, web and desktop. Connect runs the browser sign-in.
Plus/Pro/Business: pick OAuth as the connector auth; sign-in runs on connect.
OAuth: openclaw mcp login urnetwork prints the authorization link.
OAuth: first connect prints an authorize URL and opens your browser, waiting on a loopback port; hermes mcp login urnetwork re-authenticates.
opencode.json. OAuth is automatic on first use; opencode mcp auth urnetwork re-authenticates.
Agent panel → MCP Servers → Manage → edit the raw config (note serverUrl), then tap Authenticate.
Full OAuth flow, per person or per org. (Windsurf is now Devin Desktop; same place there.)
Pro/Max/Enterprise: choose OAuth at setup; works on web, Comet, and the Mac app.
settings.json (note the context_servers key), or Settings → AI → MCP Servers → Add Remote Server; Zed prompts the standard MCP OAuth flow when no header is set.
OAuth is the default for remote servers. Run /mcp inside droid to complete the sign-in.
Settings | Tools | AI Assistant | MCP → paste As JSON. No OAuth flow yet; use a static Authorization header or the mcp-remote bridge.
Settings → MCP → Add → Add Manually. Header auth only today; no OAuth in Trae yet.
OAuth: runs automatically on connect (httpUrl + oauth.enabled in ~/.qwen/settings.json); manage via /mcp.
OAuth: automatic on first use; /mcp auth urnetwork re-authenticates. (Enterprise Gemini Code Assist; individual access moved to Antigravity.)
OAuth runs during connector setup. Grok Build CLI: grok mcp add --transport http urnetwork https://mcp.bringyour.com.
AI-native MCP config: describe the server in /mcp-config and Kimi Code adds and authenticates it, with no JSON to hand-edit. (Successor to kimi-cli.)
The server uses OAuth to authenticate to your account on ur.io. The first connection opens a sign-in and your agent receives a scoped token. No keys to paste. Start with a free account and x402 will tell you when you need to upgrade.
Get Started in Minutes with a 7 day Free Trial
Manual setup with agent skill
If you don't want to use MCP or our agent doesn't support it, you can use this skill to manually use URnetwork.
$ Skills and Tools
If you are an automated agent, see the SKILL.md ↗ to wire up URnetwork in your runtime. The network needs a network account created by a person, and the person needs to share the authentication code from their control panel with you.
| Use Case | Recommended Protocol | Requirement |
|---|---|---|
| Scraping / Web Browsing | HTTPS | Best for TCP / Web. Always use HTTPS proxy unless there is a specific need to use HTTP. HTTP is usually only needed for specific test environments that do not support HTTPS. From the /network/auth-client response, inside the proxy_config_result object, use the https_proxy_url. No additional username or password are needed. |
| Low-level Sockets / UDP | SOCKSUR Pro | Supports TCP+UDP sockets with SOCKS5. From the /network/auth-client response, inside the proxy_config_result object, use the socks_proxy_url or proxy_host and proxy_port, with the username access_token (empty password). The server supports remote DNS resolution (SOCKS5H). |
| System-wide / OS Level | WireGuardUR Pro | Routes all IP packets. In the /network/auth-client request, proxy_config.enable_wg must be explicitly set to true. In the response, inside the proxy_config_result object, use the wg_config.config as the complete WireGuard config file. |
When using an HTTPS proxy, be careful that the target technology supports HTTPS. Some technologies support only HTTP and not HTTPS. If the target technology does not support an HTTPS proxy, it is preferable to consider an alternative library that does support HTTPS than to use an HTTP proxy. As a last resort, the HTTP proxy can be used.
x402 (optional)
Your agent can use x402 to pay for using URnetwork without a subscription.
$ Pay as you go with x402
The MCP server and the API both support x402, the open standard that revives HTTP 402 "Payment Required" for machines. When a job hits a plan limit, your agent can pay in stablecoins and retry automatically, with no human in the loop.
POST /x402/purchase
Content-Type: application/json
{ "sku_id": "pro_1month" }No X-PAYMENT header yet, so the server will quote, not charge.
curl -i -X POST https://api.bringyour.com/x402/purchase \
-H "Authorization: Bearer $URNETWORK_JWT" \
-d '{"sku_id": "pro_1month"}'Safe to run: the server only quotes payment terms. Nothing is charged without a signed X-PAYMENT retry.
Every x402 payment is an explicit, signed authorization for an exact amount. An agent can never spend what it didn't sign, and the default skill stops paying once it reaches the budget you set. No surprise bills, no runaway loops.