This repo hosts the downloadable pieces for running Forth MCP entirely on your own infrastructure: the relay's Docker image and the connector app that runs on each machine with a local MCP server. There's no source code here on purpose. This is a distribution point, not the project itself.
Forth MCP gives every AI client (Claude, ChatGPT, or anything else that speaks MCP) one point of contact for every MCP server your team relies on, local or already public. Self-hosting runs the whole relay on your own network: your own TLS certificate, an offline-signed license with no phone-home, and no Forth infrastructure in the path at all.
curl -O https://raw.githubusercontent.com/eladhefetz/forthmcp-releases/main/docker-compose.yml
docker compose up -dThen open http://localhost:8080 and create your admin account, this instance's only account. No license file is required to try it: a fresh install behaves as a permanent single-connector trial, so you can add a connector, attach it, and call a real tool before deciding whether to license it further.
Everything persists in the forth-mcp-data volume, including your admin account,
connectors, and encryption key. Back it up as a whole if you care about not
starting over.
Both are configured from inside the app once it's running, no need to touch the compose file: sign in, open Settings, and upload a TLS certificate or a license file there. Both take effect immediately, no restart needed.
docker compose pull
docker compose up -dThe connector is the small background service that runs on a machine with a local MCP server, and tunnels it out to your relay without opening any inbound port.
Install it with a single command, run on whichever machine has the local MCP server. That's usually a different machine from the one running the relay: the whole point of the connector is reaching a local server from wherever your relay actually runs, on the internet or on your own network.
Windows (PowerShell, run as Administrator):
irm https://raw.githubusercontent.com/eladhefetz/forthmcp-releases/main/install.ps1 | iexmacOS:
curl -fsSL https://raw.githubusercontent.com/eladhefetz/forthmcp-releases/main/install-mac.sh | bashLinux:
curl -fsSL https://raw.githubusercontent.com/eladhefetz/forthmcp-releases/main/install-linux.sh | bashEach of these registers the connector as a proper background service (Windows Service, launchd agent, or systemd user service) so it survives a reboot, then prints the address to open (http://127.0.0.1:5300) to attach it to a connector with that connector's token, shown in your relay's dashboard. That's the same page where you tell the connector which relay to talk to, see the last section below.
If you'd rather install manually, grab the zip for your platform directly and unzip it anywhere:
| Platform | Download |
|---|---|
| Windows (x64) | forthmcp-connector-win-x64.zip |
| macOS (Apple Silicon) | forthmcp-connector-osx-arm64.zip |
| macOS (Intel) | forthmcp-connector-osx-x64.zip |
| Linux (x64) | forthmcp-connector-linux-x64.zip |
After unzipping, run the Connector executable (Connector.exe on Windows) and
open http://127.0.0.1:5300 to attach it, same as above.
Every link above points at the latest release. To pin to an older one instead,
browse all releases
and swap latest/download for download/TAG in the URL, using the tag shown on
the release you want, for example:
https://github.com/eladhefetz/forthmcp-releases/releases/download/connector-v1.0.0/forthmcp-connector-osx-arm64.zip
That URL never changes once published, unlike the latest links above.
Configurable from the connector's own Settings page. Point it at your self-hosted relay's address instead of the default, at any time, without reinstalling.
Open an issue here for anything install-related: a platform that fails to install, a broken download, or just something confusing in the instructions above.