通过 MCP 连接（推荐方式）
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.)
服务器使用 OAuth 认证到您在 ur.io 的账户。首次连接会打开登录页面，您的智能体将获得限定范围的令牌。无需粘贴任何密钥。从免费账户开始，需要升级时 x402 会告诉您。
开启 14 天免费试用，几分钟即可上手
使用 agent skill 手动配置
如果您不想使用 MCP，或者您的智能体不支持 MCP，可以用这个 skill 手动使用 URnetwork。
$ 技能与工具
如果您是自动化智能体，请参阅 SKILL.md ↗ 以在您的运行时中接入 URnetwork。网络需要由真人创建的网络账户，且该用户需要将其控制面板中的认证码分享给您。
| 使用场景 | 推荐协议 | 要求 |
|---|---|---|
| 抓取 / 网页浏览 | HTTPS | 最适合 TCP / Web。除非有特定需求需要使用 HTTP，否则请始终使用 HTTPS 代理。HTTP 通常仅在不支持 HTTPS 的特定测试环境中需要。在 /network/auth-client 响应中，从 proxy_config_result 对象内使用 https_proxy_url。无需额外的用户名或密码。 |
| 底层套接字 / UDP | SOCKSUR Pro | 通过 SOCKS5 支持 TCP+UDP 套接字。在 /network/auth-client 响应中，从 proxy_config_result 对象内使用 socks_proxy_url，或使用 proxy_host 和 proxy_port，用户名为 access_token（密码为空）。服务器支持远程 DNS 解析（SOCKS5H）。 |
| 系统级 / 操作系统级 | WireGuardUR Pro | 路由所有 IP 数据包。在 /network/auth-client 请求中，必须将 proxy_config.enable_wg 显式设置为 true。在响应中，从 proxy_config_result 对象内使用 wg_config.config 作为完整的 WireGuard 配置文件。 |
使用 HTTPS 代理时，请注意目标技术需支持 HTTPS。某些技术仅支持 HTTP 而不支持 HTTPS。如果目标技术不支持 HTTPS 代理，建议优先考虑支持 HTTPS 的替代库，而非使用 HTTP 代理。万不得已时，也可以使用 HTTP 代理。
x402（可选）
您的智能体可以使用 x402 付费使用 URnetwork，无需订阅。
$ 使用 x402 按需付费
MCP 服务器和 API 都支持 x402，这一开放标准为机器复活了 HTTP 402“Payment Required”。当任务达到套餐限制时，您的智能体可以用稳定币支付并自动重试，全程无需人工介入。
POST /x402/purchase
Content-Type: application/json
{ "sku_id": "pro_1month" }还没有 X-PAYMENT 请求头，所以服务器只报价，不扣款。
curl -i -X POST https://api.bringyour.com/x402/purchase \
-H "Authorization: Bearer $URNETWORK_JWT" \
-d '{"sku_id": "pro_1month"}'可放心运行：服务器只报出支付条款。没有签名的 X-PAYMENT 重试，就不会产生任何扣款。
每笔 x402 支付都是对确切金额的显式签名授权。智能体永远无法花费未经其签名授权的金额，并且默认技能在达到您设定的预算后就会停止支付。没有意外账单，没有失控循环。