tunnel

● Active

io.github.e2e-next/tunnel

Local HTTPS proxy and mock server for app tests: record, replay, mock and break API calls

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "tunnel": {
      "command": "npx",
      "args": [
        "-y",
        "tunnel-use@3.1.1",
        "mcp"
      ]
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add tunnel -- npx -y tunnel-use@3.1.1 mcp
OpenAI Codex CLI
codex mcp add tunnel -- npx -y tunnel-use@3.1.1 mcp
VS Code
code --add-mcp '{"name":"tunnel","type":"stdio","command":"npx","args":["-y","tunnel-use@3.1.1","mcp"]}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Testing & QA
Version
3.1.1
Registry
active
Published
11/17/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 19, 2026

Looks healthy: tunnel is maintained, open source.

Maintained
Active
Last commit 5 days ago (Nov 17, 2026), 0 open issues.
Official registry
Active
Published as io.github.e2e-next/tunnel in the official MCP registry, version 3.1.1.
Source
Open source, MIT
Public repository under the MIT licence, 2 stars, 0 forks.
Runs
On your machine
A local npm package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 18, 2026
Stars
2
Forks
0
Last push
Nov 17, 2026
License
MIT

TypeScriptai-agentsandroidapi-mockingciclaude-codeclicodexe2e-testinghttp-proxyhttps-proxyiosmcpmcp-servermitmmobile-testingmock-serverrecord-replaytestingtypescriptui-testing

From the README

tunnel An AI-first mock server and HTTPS proxy: point a phone, simulator or any HTTP client at it to inspect, record, mock and replay API calls — driven by your coding agent over MCP or the CLI, or by code that embeds it. 📖 中文文档 The problem Testing a client against its real backend is slow and fragile: • The cases that matter — an empty list, a failed payment, a slow or broken response — are hard to get out of a real server on demand. • Real data drifts and test accounts get used up, so the same run gives a different result tomorrow. • A proxy such as Charles can change an answer, but by hand, one click at a time: neither a test suite nor a coding agent can drive it. • A separate mock server means pointing the app at another address and writing every answer yourself. • A CI run that quietly reaches the real backend passes for the wrong reason. What tunnel does The app keeps calling its real hosts; it only needs its HTTP proxy pointed at tunnel and tunnel's certificate trusted. tunnel decrypts the hosts you name, logs every call, and answers each endpoint the way its rule says: • Record the real answers once, each call a JSON file you can commit next to the tests. • Mock with literal JSON, or with a JavaScript handler(ctx) that can take the recorded answer and change one field of it. • Replay from the recordings without touching the network.…

Read the full README on GitHub →

The most-starred Testing & QA servers in the index, with their live-check result.

ServerStarsLast pushLive check
Keploy19,937Nov 2026Needs sign-in
e2e14,110Nov 2026Local / not checked
Mockserver5,011Nov 2026Local / not checked
Reticle1,326Nov 2026Local / not checked
Flutter Skill409Sep 2026Local / not checked

tunnel: questions people ask

Is tunnel a remote or a local MCP server?
According to its entry in the official MCP registry, tunnel ships as a local package (npm) that your client starts on your machine.
Is tunnel safe to use?
Looks healthy: tunnel is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 19, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is tunnel still maintained?
Active: the repository's last commit 5 days ago. Last push Nov 17, 2026, 2 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
How do I add tunnel to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Testing & QA →

Add the badge to your site

Show visitors that tunnel is listed here — it’s also the link we check for a free listing.

tunnel — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-e2e-next-tunnel?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="tunnel — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![tunnel — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-e2e-next-tunnel?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-e2e-next-tunnel) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-e2e-next-tunnel) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-e2e-next-tunnel)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-e2e-next-tunnel"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-e2e-next-tunnel"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-e2e-next-tunnel"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).