This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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.
Download a binary for your platform from the releases page, or build it:
go install github.com/tunnels-io/tunnels-mcp/cmd/tunnels-mcp@v0.0.2Clients 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.
Related MCP server: depot-mcp
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.
TUNNELS_TOKEN required, starts tnl_
TUNNELS_API default https://tunnels.io
TUNNELS_CLI default "tunnels" on PATH
TUNNELS_INSPECT unset. The CLI inspector is off; set an address to enable it.A config file works too, at ~/.config/tunnels/mcp.json:
{ "token": "tnl_..." }The environment wins.
{
"mcpServers": {
"tunnels": {
"command": "tunnels-mcp",
"env": { "TUNNELS_TOKEN": "tnl_..." }
}
}
}Tool | Permission |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| none |
| 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.
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.
make check
make buildNo dependencies.
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:
make release V=0.0.2MIT. See LICENSE.
This server cannot be deployed
Read-only access to your Infrly services, deploys, logs, metrics and billing.
Read-only access to a Lumin project's logs, metrics, uptime checks, alerts and infrastructure.
Browse OfficeRnD members, bookings, memberships, invoices and tickets, with optional write access.
Read-only MCP access to sessions, funnels, campaigns, errors, live visitors, and anomalies.
