Unlocalhost

Name: Unlocalhost
Author: info-arnav

作者：info-arnav版本 0.1.1i★ –i在你的电脑上运行

注册名称io.github.info-arnav/unlocalhost

安装

概览

作者提供的说明（英文原文）

Deploy localhost to a private, authenticated link from your AI coding agent.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 开发者工具
你需要填写：UNLOCALHOST_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： UNLOCALHOST_URL, UNLOCALHOST_TOKEN

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "unlocalhost": {
      "command": "npx",
      "args": [
        "-y",
        "@unlocalhost/unlocalhost"
      ],
      "env": {
        "UNLOCALHOST_URL": "your-value",
        "UNLOCALHOST_TOKEN": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add unlocalhost --env UNLOCALHOST_URL=your-value --env UNLOCALHOST_TOKEN=your-value -- npx -y @unlocalhost/unlocalhost

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "unlocalhost": {
      "command": "npx",
      "args": [
        "-y",
        "@unlocalhost/unlocalhost"
      ],
      "env": {
        "UNLOCALHOST_URL": "your-value",
        "UNLOCALHOST_TOKEN": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "unlocalhost": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@unlocalhost/unlocalhost"
      ],
      "env": {
        "UNLOCALHOST_URL": "your-value",
        "UNLOCALHOST_TOKEN": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

UNLOCALHOST_URL env
Base URL of the unlocalhost instance to talk to. Defaults to the hosted instance. Set this to point the tools at your own self hosted deployment.
UNLOCALHOST_TOKEN 机密 env
API token. Normally written by the unlocalhost_login tool after you approve the device in a browser, so you should not need to set this by hand.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 info-arnav 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“开发者工具”中的其他服务器比较i

星标数多于此分类中其他 1389 个服务器的 0%
发布到注册中心的时间比此分类中其他 1389 个服务器的 35% 更新
基础检查结果等于或优于此分类中其他 1389 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Unlocalhost 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：UNLOCALHOST_TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.1）于3个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：GitHub, Desktop Commander, Cloudflare MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

GitHub

作者：github

Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.

电脑或云端★ 34,245MIT3天前更新

安装

Desktop Commander

作者：wonderwhy-er

MCP server for terminal commands, file operations, and process management

在你的电脑上运行★ 10,225MIT15天前更新

安装

Cloudflare MCP

作者：cloudflare

Cloudflare MCP servers

在云端运行★ 4,446Apache-2.014个月前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

unlocalhost

Turn localhost into a link only the people you name can open.

Website · Docs · MIT licensed · Self hostable

The problem

Your coding agent can write the whole application. It cannot host it, because hosting needs a server, a domain, a certificate, and a login system. So people reach for whatever is fastest, and that is where things go wrong: a public URL with no sign in, an API key committed by accident, or auth bolted on at the end by someone who has never written auth.

unlocalhost closes that gap. You say one sentence to the agent you already have open, and you get back a real URL with a guest list in front of it.

you    deploy this and let sarah@gmail.com in

agent pushed your code to a private repo agent building agent live at sarahs-todo.unlocalhost.tech agent sarah@gmail.com can sign in and open it

How it works

You add unlocalhost to your coding agent as an MCP server and sign in once with GitHub.
You tell the agent to deploy, and name who is allowed in.
Your agent pushes the code using your own git credentials. unlocalhost never holds write access to anything.
We clone read only, scan for committed secrets and refuse to continue if we find any, then build and run it.
Visitors sign in with GitHub or Google. Their verified email is checked against the guest list before the request ever reaches your app.

What makes it different

	Tunnel (ngrok)	Platform (Vercel)	unlocalhost
Survives closing laptop	No	Yes	Yes
Private by default	No	No	Yes
Auth you have to write	All of it	All of it	None
Runs on your own server	No	No	Yes

Quick start

claude mcp add unlocalhost -- npx -y @unlocalhost/unlocalhost

Or in any MCP client config:

"mcpServers": { "unlocalhost": { "command": "npx", "args": ["-y", "@unlocalhost/unlocalhost"] } } }

Then ask your agent to sign in to unlocalhost, and deploy.

Self hosting

The hosted service runs this exact code. Nothing is held back, there is no phone home, and no license check.

git clone https://github.com/info-arnav/unlocalhost.git

cd unlocalhost/deploy cp .env.example .env # fill it in docker compose --env-file .env run --rm migrate docker compose --env-file .env up -d

You need a domain with wildcard DNS, a DNS provider API token for wildcard TLS, a GitHub App, and a Google OAuth client. The full walkthrough is in docs/server-setup.md.

Architecture

internet :443 → Caddy → auth-gate /verify → activator → Dokku → your app

Package	Job
`web`	Landing page, sign in screens, docs
`server/gateway`	Public API ingress, CORS, rate limiting, request ids
`server/services/auth-gate`	OAuth, sessions, and the allowlist check on every request
`server/services/control-plane`	Apps, sharing, GitHub App, deploy pipeline
`server/services/activator`	Wakes sleeping apps, puts idle ones back to sleep
`server/services/mcp-server`	The `unlocalhost` npm package your agent talks to
`server/shared`	Database, logging, crypto, errors, sessions

Borrowed rather than built: Dokku and Nixpacks turn a repository into a running container, Caddy handles wildcard TLS. The novel part is small on purpose.

Security

Apps are private until you name someone. Removing them revokes access at once.
Every deploy is scanned for committed secrets and refused if any are found.
Sign in is enforced at the edge, before a request reaches your app.
Environment variables are encrypted at rest with AES 256 GCM.
We hold read only access, and only to repositories you pick.

Found a vulnerability? Please follow SECURITY.md rather than opening a public issue.

Contributing

Read CONTRIBUTING.md first. In short: every backend module follows routes → controller → service → repository, code carries no comments, and there are no test files. Verification is done by running things.

Licence

MIT. See LICENSE.