Read a tunnels.io account and put local ports online. Lists only the tools the token was granted.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON ▾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for tunnels.io, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Documentation Overview
tunnels-mcp
MCP server for tunnels.io.
It runs locally, holds one CLI token, and gives an assistant read access to the account. It can also open a tunnel.
Install
Download a binary for your platform from the releases page, or build it:
Clients that take MCP bundles, such as Claude Desktop, can install
tunnels-mcp-<version>.mcpb from the same page. It asks for the token.
The server is listed in the MCP Registry as io.github.tunnels-io/tunnels-mcp.
Token
Create one at tunnels.io/account/tokens. Tick the permissions you want.
Skipping a permission is not a broken tool. The server reads the token's permissions at startup and lists only the tools that work.
An older all-access token (*) works for everything except billing, domains
and cloud apps. Those three services refuse *, so the server does not list
their tools for such a token. Make a token on the page above to reach them.
A config file works too, at ~/.config/tunnels/mcp.json:
The environment wins.
Client setup
Tools
| Tool | Permission |
|---|---|
list_tunnels | tunnels:read |
get_usage | usage:read |
get_metrics | usage:read |
get_account | account:read |
list_tokens | tokens:read |
list_invoices | billing:read |
list_domains | registrar:read |
list_notifications | notifications:read |
list_cloud_apps | cloud:read |
start_tunnel | none |
stop_tunnel | none |
Reads only, apart from the last two. Those shell out to the tunnels CLI, which
must be on PATH. No tool changes a plan, buys a domain or deploys anything.
start_tunnel takes http (the default, served as HTTPS on the public URL) or
tcp.
Token handling
The token goes to tunnels.io in a Bearer header, and to the CLI through the environment. Never a command line. Never a log. Never a tool result.
Error bodies are redacted before they are shown.
The server contacts tunnels.io and nothing else.
Build
No dependencies.
Release
Push a tag such as v0.0.2. The release workflow builds six binaries and
the MCPB bundle, creates the GitHub release, and publishes server.json to the
MCP Registry. To build the same files locally, on macOS:
Licence
MIT. See LICENSE.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Tunnels.io
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/tunnels-io)HTML Embed
<a href="https://allmcps.com/mcp/tunnels-io"><img src="https://allmcps.com/api/badge/tunnels-io?style=directory" alt="Tunnels.io on AllMCPs" /></a>