Integration

Ngrok integration

Secure tunnel and ingress platform API. Create tunnels to expose local servers, manage reserved domains, configure TLS certificates, and monitor traffic. Essential for development webhooks, API testing, and secure remote access.

Connect Ngrok How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Ngrok.Built from the 10 Ngrok tools below, on the connection you add once.

Common Ngrok use cases

API access
key rotation
domain cleanup
key management
tunnel details
edge management
persistent URLs
domain management
tunnel monitoring
session monitoring

What you can do with Ngrok

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Apikey, 3 operations

create_api_keyCreate api keyPOSTCreates a new API key for authentication.
delete_api_keyDelete api keyDELETERevokes an API key immediately.
list_api_keysList api keysGETLists all API keys in the account.

Reserveddomain, 3 operations

create_reserved_domainCreate reserved domainPOSTReserves a persistent domain for tunnel endpoints.
delete_reserved_domainDelete reserved domainDELETEReleases a reserved domain.
list_reserved_domainsList reserved domainsGETLists all reserved domains in the account.

Tunnel, 2 operations

get_tunnelGet tunnelGET[Deprecated] Retrieves detailed information about a specific tunnel. Use GET /endpoints/{id} instead.
list_tunnelsList tunnelsGET[Deprecated] Lists all currently active tunnels in the account.

Edge, 1 operation

list_edgesList edgesGETLists HTTPS edge configurations.

Tunnelsession, 1 operation

list_tunnel_sessionsList tunnel sessionsGETLists all tunnel agent sessions.

Ngrok API rate limits

120 requests per minute

Rate limits vary by plan

These are the limits Ngrok documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Ngrok documentation for current values.

Use Ngrok from Claude Code, Cursor or Codex

Connect Ngrok in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ngrok operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Ngrok

Create your workspace
Sign up free. Nothing to install.
Connect Ngrok once
Add your Ngrok connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Ngrok integration FAQ

What can you do with the Ngrok integration?

LiveContext exposes 10 operations on Ngrok, covering apikey, reserveddomain, tunnel and edge. Common uses include API access, key rotation and domain cleanup.

What are the Ngrok API rate limits?

Ngrok documents 120 requests per minute. Rate limits vary by plan Limits are set by Ngrok and can depend on your plan.