Uso de MCP

Usa el modo MCP para exponer endpoints MCP locales a clientes remotos. MCP esta disponible en planes Pro y Business.

Requisito del plan: El modo MCP requiere una API key autenticada en Pro o Business.

1. Instalar CLI

$ npm install -g instatunnel

2. Autenticarse (usuarios nuevos vs existentes)

Usuario nuevo

$ instatunnel auth login -e you@example.com

# Verify email from inbox and copy API key from verification page

$ instatunnel auth set-key "it_your_api_key"

Usuario existente

$ instatunnel auth show-key --reveal --copy

# If key is not saved locally:

$ instatunnel auth login -e you@example.com

# Use recovery email, then save the new/current key:

$ instatunnel auth set-key "it_your_api_key"

$ Set-Clipboard "it_your_api_key" # Windows PowerShell helper

$ instatunnel auth set-key "$(Get-Clipboard)"

$ pbpaste | xargs -I {} instatunnel auth set-key "{}" # macOS

$ xclip -o -selection clipboard | xargs -I {} instatunnel auth set-key "{}" # Linux

2a. Usa el asistente MCP del dashboard (recomendado)

Prefieres un flujo guiado? Abre tu dashboard y usa MCP Setup Wizard v2 dentro de CLI Updates, MCP, and 2026 Best Practices. dashboard.

Verifica elegibilidad MCP del plan antes de configurar.
Genera el comando exacto instatunnel ... --mcp --transport v2 con tu puerto y subdominio.
Genera JSON de un clic para VS Code, Cursor, Claude Desktop, Windsurf, Codex y Gemini Antigravity.

3. Inicia el tunel MCP (v1 por defecto)

v1 es el transporte por defecto. Es la opcion mas compatible para HTTP y trafico estilo webhook.

$ instatunnel 8787 --mcp

$ instatunnel 8787 --mcp --subdomain my-mcp

4. Usa transporte streaming v2 cuando sea necesario

Usa v2 cuando necesites streaming (MCP Streamable HTTP, respuestas largas o flujos tipo server-push). Si tienes dudas, empieza con v1 y cambia a v2 solo para clientes de streaming.

$ instatunnel 8787 --mcp --transport v2

$ instatunnel 8787 --mcp --transport v2 --subdomain my-mcp

Compatibilidad: --transport v2 requires newer InstaTunnel CLI versions (1.1.7+). Recommended update: npm install -g instatunnel@latest.

5. Header de token MCP opcional (despliegue gradual)

InstaTunnel soporta header de token MCP para defensa en profundidad. En el despliegue gradual actual, tu workspace puede iniciar en modo aviso y despues pasar a modo estricto.

$ export INSTATUNNEL_MCP_TOKEN="your-shared-secret"

$ instatunnel 8787 --mcp --transport v2

5a. Genera YOUR_MCP_TOKEN

Genera un token fuerte y usalo como YOUR_MCP_TOKEN en headers Authorization del JSON MCP.

$ node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"

$ node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" | Set-Clipboard # Windows

$ node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" | pbcopy # macOS

$ node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" | xclip -selection clipboard # Linux

6. Configura tu cliente/servidor MCP

Usa la URL HTTPS generada en la configuracion de tu cliente MCP y apunta a la ruta esperada por tu servidor MCP local.

https://your-subdomain.instatunnel.my

6a. Necesitas headers de Authorization?

No para servidores MCP locales por stdio. Alli no se usan headers.
No si tu servidor MCP remoto no exige auth.
Si solo cuando tu servidor MCP espera bearer token (recomendado en endpoints publicos).
Aplica a VS Code, Cursor, Claude Desktop, Windsurf, Codex y Gemini Antigravity: el cliente no obliga bearer auth; la politica la define el servidor.

7. Generador MCP de un clic

Genera y copia JSON listo para usar para VS Code, Cursor, Claude Desktop, Windsurf, Codex y Gemini Antigravity.

One-Click MCP Config Generator

Generate IDE-ready JSON for VS Code, Cursor, Claude Desktop, Windsurf, Codex, and Gemini Antigravity with endpoint and token header.

Tunnel subdomainMCP token

MCP Endpoint

https://your-subdomain.instatunnel.my/mcp

Target: .vscode/mcp.json (workspace)

{
  "mcpServers": {
    "instatunnel-remote": {
      "type": "streamable-http",
      "url": "https://your-subdomain.instatunnel.my/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_TOKEN"
      }
    }
  }
}

headers.Authorization is not required by MCP clients by default. Add it only when your MCP server expects bearer-token auth. For local stdio MCP servers, headers are not used.

Token helper

Generate a strong token, paste it into YOUR_MCP_TOKEN, and use the same value in your local MCP server auth.

node -e "console.log(require('crypto').randomBytes(32).toString('hex'))" | Set-Clipboard

Loading MCP setup...

Notas

v1 sigue siendo el transporte por defecto por compatibilidad.
Si tienes dudas, empieza con v1.
Usa v2 para MCP Streamable HTTP y respuestas largas en streaming.
--transport v2 requiere CLI 1.1.7+; manten actualizado con npm install -g instatunnel@latest.
Los tuneles MCP tienen protecciones mas estrictas, incluyendo limites de tasa especificos.
Usa instatunnel --stats para uso de cuenta e instatunnel --logs para polling de logs.
Usa autenticacion y evita exponer herramientas sensibles en publico.

MCP FAQ (Localhost, Webhooks, IDE Setup)

Common setup and troubleshooting questions for VS Code, Cursor, Claude Desktop, Windsurf, Codex, and Gemini Antigravity.

Do VS Code, Cursor, Claude Desktop, Windsurf, Codex, or Gemini Antigravity require Authorization headers by default?

No. The client usually does not force bearer headers. Add "Authorization": "Bearer YOUR_MCP_TOKEN" only if your remote MCP server enforces token auth. For local stdio MCP servers, headers are not used.

Which endpoint should I use with InstaTunnel?

Use: https://YOUR-SUBDOMAIN.instatunnel.my/mcp. Start your local MCP server first, then run: instatunnel 8787 --mcp --transport v2 --subdomain YOUR-SUBDOMAIN.

What is the difference between local stdio MCP and remote HTTP MCP?

Local stdio is process-to-process on your machine, with no public URL. Remote HTTP MCP is reachable via URL and is required when an IDE or agent needs to access your MCP server from another network context.

Why do I get "failed to reach local server localhost:8787"?

InstaTunnel can reach the public tunnel, but your local app is not listening on the forwarded port. Start your MCP server locally on the same port (for example 8787) and retry.

Can I use this for localhost sharing and webhook testing?

Yes. For generic webhook testing, use normal HTTP tunnels (for example instatunnel 3000 --subdomain webhook-demo). For MCP tools, use MCP mode with --mcp --transport v2 and the /mcp endpoint.

Which transport should I use: v1 or v2?

v1 is default and most compatible, so start there if you are unsure. Use v2 when you need Streamable HTTP behavior (long-lived streaming/tool responses). Recommended: instatunnel 8787 --mcp --transport v2. Note: --transport v2 requires newer CLI versions (1.1.7+). Update with npm install -g instatunnel@latest.

Why do I get "MCP mode is available on Pro and Business plans"?

MCP mode is gated by plan. Upgrade to Pro/Business, then rerun your command with the same saved API key.

Where do I configure MCP clients?

Use each client's MCP settings area. The JSON shape from the generator works for common MCP clients. For Codex, you can also register MCP servers via codex mcp add.

Official references

Loading MCP FAQ...

Donde debo empezar en la documentacion de InstaTunnel?

Evidencia y confianza

Cadencia de releases

Controles de seguridad

Runbooks de confiabilidad

Documentacion

Uso de MCP

1. Instalar CLI

2. Autenticarse (usuarios nuevos vs existentes)

2a. Usa el asistente MCP del dashboard (recomendado)

3. Inicia el tunel MCP (v1 por defecto)

4. Usa transporte streaming v2 cuando sea necesario

5. Header de token MCP opcional (despliegue gradual)

5a. Genera YOUR_MCP_TOKEN

6. Configura tu cliente/servidor MCP

6a. Necesitas headers de Authorization?

7. Generador MCP de un clic

One-Click MCP Config Generator

Notas

MCP FAQ (Localhost, Webhooks, IDE Setup)

Necesitas una ruta rapida?

One-Click MCP Config Generator

MCP FAQ (Localhost, Webhooks, IDE Setup)