front-proxy

Name: front-proxy
Author: gutomezencio

by gutomezencioversion 0.8.2i★ –iRuns on your computer

Registry nameio.github.gutomezencio/front-proxy

Install

Overview

Description from the maker (original English)

Map local domains (and HTTPS) to apps on local ports, OS-wide, via /etc/hosts and a reverse proxy.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "front-proxy": {
      "command": "npx",
      "args": [
        "-y",
        "front-proxy",
        "mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add front-proxy -- npx -y front-proxy mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "front-proxy": {
      "command": "npx",
      "args": [
        "-y",
        "front-proxy",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "front-proxy": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "front-proxy",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account gutomezencio, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32655 servers in this category
Published to the registry more recently than 57% of the other 32655 servers in this category
Basic checks equal to or better than 100% of the other 32655 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is front-proxy safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.8.2) reached the registry 29 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, SuperCollider

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

SuperCollider

by Tok

Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

front-proxy

Reach apps on local ports, like localhost:3000, through real-looking domains, like local-dev.mylivedomain.com, over HTTP or HTTPS.

While it runs, front-proxy adds your domains to /etc/hosts, pointing them at 127.0.0.1, and runs a reverse proxy on ports 80 and 443. When it stops, it removes them. The proxy reads the Host header of each request and forwards it to the port you mapped to that domain. HTTPS uses locally trusted certificates from mkcert. Because the mapping lives in the OS, it works in every browser and tool on your machine, not just one.

  Browser, curl, Playwright...

│ │ https://local-dev.mylivedomain.com ▼ ┌───────────────────────────────────────────────┐ │ /etc/hosts │ │ 127.0.0.1 local-dev.mylivedomain.com │ └───────────────────────────────────────────────┘ │ │ 127.0.0.1:443 (or :80 for http) ▼ ┌───────────────────────────────────────────────┐ │ front-proxy │ │ 1. TLS with the domain's mkcert certificate │ │ 2. Host header → port, from proxyHosts.json │ │ local-dev.mylivedomain.com → 3000 │ │ (unknown host → 502) │ └───────────────────────────────────────────────┘ │ │ http://127.0.0.1:3000 ▼ Your local app

Why

Some third-party services only accept requests from an allowlist of domains (Stripe and Google Tag Manager, for example), and some APIs block localhost with CORS. Browser extensions can fake a domain for one browser. front-proxy works for the whole OS, so it also covers other browsers, CLI tools and headless Playwright runs with no extra configuration.

Requirements

Node.js 22.12 or newer
macOS or Linux (it edits /etc/hosts and uses sudo)
mkcert, only for HTTPS (brew install mkcert on macOS)

Installation

npm install -g front-proxy

The front-proxy command is now available in your terminal.

If npm install -g fails with EACCES, your npm global folder is owned by root. That's common with the system Node on Linux or the official macOS installer. Use a Node installed with nvm or Homebrew, or run sudo npm install -g front-proxy.

To update:

npm update -g front-proxy

Your domains and certificates live in ~/.front-proxy (see Configuration), so updates and reinstalls keep them.

To run it from a clone instead, see Development.

Usage

front-proxy add local-dev.livedomain.com:3000   # map a domain to a local port

front-proxy # start the proxy

Then open http://local-dev.livedomain.com (or https:// once you've set up certificates).

Command	Description	Needs sudo
`front-proxy`	Start the proxy on ports `80` and `443`, adding your domains to `/etc/hosts` until it stops	Yes
`front-proxy --persist-hosts`	Same, but keep the domains in `/etc/hosts` after the proxy stops (`-p` for short)	Yes
`front-proxy --no-admin`	Start without the admin page	Yes
`front-proxy add`	Add a domain to the proxy config	No
`front-proxy remove`	Remove a domain from the proxy config	No
`front-proxy list`	List the configured domains	No
`front-proxy generate-certs [host]`	Create HTTPS certificates with mkcert, for one domain or all of them	No
`front-proxy mcp`	Run the MCP server for code assistants, on stdio	No
`front-proxy --help`	Show the help	No

Only starting the proxy asks for your password through sudo, because it binds ports 80/443 and edits /etc/hosts. The password isn't stored.

The domains go into a single block in /etc/hosts:

# <FRONT-PROXY-HOSTS>

> local-dev.livedomain.com < Host added by front-proxy

127.0.0.1 local-dev.livedomain.com #

Stopping the proxy (Ctrl+C) removes the block, unless you started it with --persist-hosts. If the proxy didn't stop cleanly (it crashed or was killed), the block stays until the next start. Each start replaces any block it finds with a fresh one. add and remove only change the config, so restart the proxy to apply them.

Requests for a domain that isn't configured get a 502 response.

Hosts must be valid hostnames (letters, digits, hyphens and dots, like myapp.local). IP addresses, localhost, front-proxy.localhost and ports 80/443 (the proxy's own) are rejected. Entries in proxyHosts.json that don't pass these checks are skipped with a warning.

Admin page

While the proxy runs, open http://front-proxy.localhost to manage your domains in the browser. The page:

lists the configured domains, with a dot showing whether something is listening on each port
adds and removes domains, and changes a domain's port
shows which certificate each domain uses, with the generate-certs command to copy when it has none
links to each active domain over HTTP (and HTTPS when it's on)

Changes are saved to proxyHosts.json right away, like the CLI commands. The page then shows a banner until they're active: click Apply now to reload the routes, certificates and /etc/hosts block without restarting, or restart front-proxy.

The proxy runs as root, so the page only accepts:

requests from this machine (127.0.0.1/::1), with the front-proxy.localhost host, which blocks LAN clients and DNS rebinding
changes sent from the page itself: its Origin, a JSON body and a random token generated each time the proxy starts

Its responses use a strict Content Security Policy and can't be framed. To turn the page off, start with front-proxy --no-admin.

For HTTPS on the admin page, the default certificate must include front-proxy.localhost. generate-certs adds it when it creates the default certificate. If yours was created by an older version, delete ~/.front-proxy/keys/_private-default-*.pem and run front-proxy generate-certs again.

MCP server

front-proxy mcp runs a Model Context Protocol server on stdio, so code assistants (Claude Code, Cursor, VS Code, Codex, Windsurf…) can manage your domains for you. For example, they can map the app they just started to a domain and check that it answers. It's listed in the MCP Registry as io.github.gutomezencio/front-proxy.

Claude Code: install the plugin, which adds the MCP server and a skill that tells Claude when front-proxy helps (allowlisted domains, CORS, cookies, local HTTPS):

claude plugin marketplace add gutomezencio/front-proxy

claude plugin install front-proxy@front-proxy

Or add only the MCP server: claude mcp add front-proxy -- npx -y front-proxy mcp.

Claude Desktop: download front-proxy.mcpb from the latest release and open it.

Codex: codex mcp add front-proxy -- npx -y front-proxy mcp.

Other clients take the same command in their MCP config:

"mcpServers": { "front-proxy": { "command": "npx", "args": ["-y", "front-proxy", "mcp"] } } }

If you installed front-proxy globally, front-proxy mcp works too. Both share the config in ~/.front-proxy, but the proxy itself still runs from the global install (see below).

Tool	What it does
`list_hosts`	List the configured domains, their ports and certificate status
`add_host`	Map a domain to a local port (same checks as `front-proxy add`)
`update_host`	Point a domain to another port
`remove_host`	Remove a domain
`generate_certs`	Create HTTPS certificates with mkcert, for one domain or all of them
`proxy_status`	Whether the proxy runs, whether HTTPS is on, whether changes are waiting, and which apps are listening
`apply_config`	Load the saved config into the running proxy, like Apply now on the admin page

The MCP server runs as you, without sudo, like add and remove. Its changes are saved to proxyHosts.json. To apply them, it calls the running proxy's admin API from 127.0.0.1 with the same per-run token and Origin as the admin page. Some things are left to you:

Starting and stopping the proxy needs your password, so the assistant asks you to run front-proxy.
apply_config needs the admin page on (the default). With --no-admin, restart the proxy to apply changes.
generate_certs can't type your password, so run mkcert -install once in a terminal before using it.

HTTPS

HTTPS on port 443 needs locally trusted certificates, which front-proxy creates with mkcert:

front-proxy generate-certs                            # every configured domain

front-proxy generate-certs local-dev.livedomain.com # a single domain

The first run installs mkcert's local CA so browsers trust the certificates. It also creates a default certificate for localhost and front-proxy.localhost. Each domain then gets its own certificate, which the proxy serves through SNI. Domains without their own

Only the beginning is shown; read the rest in the repo

front-proxy

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

SuperCollider

README from the maker

Why

Requirements

Installation

Usage

> local-dev.livedomain.com < Host added by front-proxy

Admin page

MCP server

HTTPS