Loopback MCP server
Commit Nov 6, 2026Provides a self-hosted gateway to connect AI agents to files, shell commands, and SSH targets on remote or local machines.
Also known as p5n-n3t/loopback
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 6, 2026
- License
- MIT
What is Loopback MCP?
Loopback provides a self-hosted gateway to connect AI agents to files, shell commands, and SSH targets on remote or local machines.
Summary generated from the project's README
About Loopback MCP server
Connecting AI agents to your local files, shell commands, and remote servers is what Loopback enables through a self-hosted gateway. It provides a way for MCP clients to interact with machines you control by exposing a single authenticated Streamable HTTP endpoint and a management dashboard. You can run it on localhost for local access or use tools like Tailscale, Cloudflare Tunnel, or ngrok to connect remote clients to your hardware.
Developers can manage a fleet of machines by registering Loopback nodes or plain SSH targets, applying specific policies to each. Security is handled via OAuth 2.1 with PKCE or revocable API tokens, alongside filesystem roots and command approvals. The system supports Linux, macOS, and Windows, offering different levels of shell isolation such as Landlock or Seatbelt depending on the operating system. It also includes execution traces to help you inspect policy decisions and exit statuses.
Written from the project's README. Every use case is checked against a quote from it.
README
View on GitHubLoopback
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
| Use case | Loopback gives you |
|---|---|
| Work on your machine from an MCP client | File and document tools, shell commands, background jobs, and persistent terminals on supported hosts. Tool reference |
| Manage several machines through one gateway | Register Loopback nodes or plain SSH targets and set a separate policy for each. Fleet and SSH |
| Control what a client can access | OAuth 2.1 with PKCE or revocable API tokens, filesystem roots, tool permissions, command approvals, and OS sandboxing where available. Authentication · Permissions |
| Connect from another network | Use Tailscale Serve for private tailnet access, Tailscale Funnel, Cloudflare Tunnel, or a fixed ngrok hostname for public HTTPS, or a reverse proxy you manage. Deployment · ngrok setup |
| Diagnose failed or interrupted calls | Inspect gateway receipts, policy decisions, dispatch, and exit status. Export redacted JSON or Markdown from Execution traces. Execution traces |
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
- Open the dashboard and review the tools, filesystem roots, and shell policy you want the client to use.
- 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.
- 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
| Gateway host | Service manager | Shell isolation and limits |
|---|---|---|
| Linux, x86_64 and arm64 | systemd user service where available | Landlock or bubblewrap, depending on the host. |
| macOS 13+, Intel and Apple Silicon | launchd LaunchAgent | Seatbelt where sandbox-exec is available. |
| Windows 10/11, x86_64 | Task Scheduler at logon | No OS sandbox for arbitrary shell commands and no persistent PTY. |
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.
Loopback MCP questions
How can I connect to a machine from another network?
You can use Tailscale Serve, Tailscale Funnel, Cloudflare Tunnel, a fixed ngrok hostname, or a managed reverse proxy.
What authentication methods does Loopback support?
Loopback supports OAuth 2.1 with PKCE and revocable API tokens.