Loopback

Self-hosted Model Context Protocol (MCP) gateway for your computers and servers.

Give an MCP client scoped access to files, shell commands, jobs, terminals, and SSH targets on machines you control. Loopback serves one authenticated Streamable HTTP endpoint and a dashboard. Start on localhost, then choose how to expose the gateway if a remote client needs it.

Install · Connect a client · Supported platforms · Documentation · Download the release

What you can do

Related MCP server: InstaServer

Install

Install on the machine the client should access. Use a regular user account and start with local ingress. Use the GitHub release assets for a versioned download, or follow the checkout commands below. See installation details for prerequisites, noninteractive options, and distribution status.

Linux and macOS

Requires Git, Bash, and Python 3.11+ with venv. The installer can offer prerequisite installation through supported package managers.

git clone https://github.com/p5n-n3t/loopback.git
cd loopback
./install.sh --non-interactive --ingress local

Windows 10 and 11

Requires Git, PowerShell, and Python 3.11+. Omit --non-interactive to allow the installer to offer Python installation through winget.

git clone https://github.com/p5n-n3t/loopback.git
Set-Location loopback
.\install.ps1 --non-interactive --ingress local

See Windows limitations for shell isolation, persistent terminals, and Task Scheduler.

Verify the installation

Open a new terminal if the launcher directory was just added to your PATH.

loopback status
loopback url
loopback dashboard --open

Use the URL printed by loopback url as the MCP server URL. The local default is http://127.0.0.1:2026/mcp. Run loopback doctor --deep if setup fails. For an existing installation, follow the upgrade guide.

Connect a client

1. Open the dashboard and review the tools, filesystem roots, and shell policy you want the client to use.

2. Add the server URL to an MCP client that supports Streamable HTTP. Use OAuth when supported. For a bearer-only client, create a revocable API token with the scopes it needs.

3. Start with a read-only tool such as machine_info, then check its receipt in Execution traces.

For a hosted client, configure HTTPS ingress reachable from that client. Loopback records calls that reach the authenticated gateway. A hosted client can reject an action before dispatch, in which case there may be no gateway receipt. See web agent setup and client capabilities.

Ask in plain English

Once connected, tell the client what you want done in ordinary language. Mention the machine, the folder or resource, and the limits of the task.

• “Using Loopback on the local machine, summarize the README in my project folder. Read only.”

• “On my registered build server, check available disk space and show the three fullest filesystems. Do not change anything.”

• “Check the status of the last Git commit in my project, then show the exit status and any Loopback receipt returned by the call.”

Loopback does not require a subscription. The chat or IDE still needs support for custom MCP servers. Claude Free includes one remote custom connector. In ChatGPT Web, check whether your account can add a custom MCP server under Plugins and use it in the intended conversation. The Plugins directory is available across plans, while a specific connector's tools depend on the account and conversation surface. See client and account requirements.

Use responsibly

An eligible web chat can use Loopback for coding tasks such as reading a checkout, running tests, and applying authorized edits. The web client still chooses the available models, thinking levels, tools, and approval flow. Everyday chat allowances do not grant unlimited tool runs or Codex usage. Use supported connection methods and respect provider limits and safety controls. Only connect machines and accounts you are authorized to operate. You are responsible for the access you grant and the actions you approve. Loopback is provided as-is under the MIT license. See ChatGPT Web vs. Codex CLI.

Supported platforms

GitHub CI runs the Python suite on Ubuntu with Python 3.11 and 3.13. See the platform guide for capability differences and validation scope.

Documentation

• Set up · Installation, configuration, deployment, upgrades

• Connect and secure · Authentication, permissions and sandboxing, Cloudflare, Tailscale

• Operate · Dashboard, fleet, independent workers, execution traces, troubleshooting

• Integrate · Tools, agent skills, plugin packaging, architecture, admin API

See the full docs index, changelog, and security policy. Loopback is available under the MIT license.