Unlocalhost

io.github.info-arnavPublished by GitHub account info-arnavv0.1.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

An MCP server that lets a coding agent deploy a localhost app to a private, sign-in-protected link with a named guest list.

What you can do
Sign in to the unlocalhost service through a browser device approval, with the token stored automatically for later calls. Ask the agent to deploy the current project, which pushes code with your own git credentials, scans for committed secrets, builds and runs it. Name who may open the deployed app, with visitors signing in via GitHub or Google and their verified email checked against the guest list. Manage sharing and access to deployed apps, with removal revoking access immediately. Point the tools at a self-hosted unlocalhost instance instead of the hosted one.
When to use it
Useful when you have built an app with a coding agent and want a real, persistent URL that only invited people can open, without writing authentication or running your own server. Also suited to teams that prefer self-hosting the deployment service.
Requirements
Runs locally via npx from the npm package, so Node.js is needed. A GitHub sign-in through the browser is required once. The UNLOCALHOST_TOKEN secret is normally written by the login tool after device approval; UNLOCALHOST_URL optionally points at a self-hosted instance. Self-hosting additionally needs a domain with wildcard DNS, a DNS provider API token, a GitHub App and a Google OAuth client.
Before you install
Deploying pushes your code to a repository and runs it on the service, so review what is sent. The service clones repositories read-only and scans for committed secrets, refusing deploys that contain them, but secrets should still be kept out of the repo. Guest-list changes control who can access the app; removing someone revokes access at once. The token grants access to your unlocalhost account and should be kept private.

Installation

In SourceWeft

  1. Open Unlocalhost in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[unlocalhost]

unlocalhost

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

Sign in is built in, so you write no auth code and touch no servers.

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 [email protected] in
agent  pushed your code to a private repoagent  buildingagent  live at sarahs-todo.unlocalhost.techagent  [email protected] can sign in and open it

How it works

  1. You add unlocalhost to your coding agent as an MCP server and sign in once with GitHub.
  2. You tell the agent to deploy, and name who is allowed in.
  3. Your agent pushes the code using your own git credentials. unlocalhost never holds write access to anything.
  4. We clone read only, scan for committed secrets and refuse to continue if we find any, then build and run it.
  5. 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 laptopNoYesYes
Private by defaultNoNoYes
Auth you have to writeAll of itAll of itNone
Runs on your own serverNoNoYes

Quick start

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

Or in any MCP client config:

json
{  "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.

bash
git clone https://github.com/info-arnav/unlocalhost.gitcd unlocalhost/deploycp .env.example .env      # fill it indocker compose --env-file .env run --rm migratedocker 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
PackageJob
webLanding page, sign in screens, docs
server/gatewayPublic API ingress, CORS, rate limiting, request ids
server/services/auth-gateOAuth, sessions, and the allowlist check on every request
server/services/control-planeApps, sharing, GitHub App, deploy pipeline
server/services/activatorWakes sleeping apps, puts idle ones back to sleep
server/services/mcp-serverThe unlocalhost npm package your agent talks to
server/sharedDatabase, 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.

Source: README.md at commit 083d851

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts