← All integrations

ngrok MCP server

18 operations0 webhooks

Manage ngrok cloud endpoints and their traffic policies, reserve custom domains, list agent tunnels and API keys, and manage event subscriptions that deliver ngrok events to your destinations.

Try ngrok with your agent

Connect ngrok, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in ngrok on my account, then run one read-only example and show me the result.

Runs once, when you ask

ngrok tools and triggers

Tools are what your agent can do in ngrok through Corsair's MCP server. Triggers are the ngrok events a routine can start from.

Domains

  • CreateWrite

    Reserve a hostname and return the CNAME target to point DNS at; certificate issuance starts once it resolves

    domains.create

  • DeleteDestructive

    Release a reserved domain, which stops it resolving through ngrok; another account can then claim it

    domains.delete

  • GetRead-only

    Read one reserved domain, including its certificate provisioning status

    domains.get

  • ListRead-only

    List reserved domains with their CNAME target and certificate state

    domains.list

  • UpdateWrite

    Change a reserved domain’s description, certificate, management policy or allowed IPs

    domains.update

Endpoints

  • CreateWrite

    Create a cloud endpoint at a URL you own (e.g. your ngrok dev domain); its required Traffic Policy decides what happens to requests, and it serves immediately

    endpoints.create

  • DeleteDestructive

    Delete a cloud endpoint; its public URL stops resolving and ngrok has no restore call

    endpoints.delete

  • GetRead-only

    Read one cloud endpoint by id

    endpoints.get

  • ListRead-only

    List cloud endpoints with their public URL, upstream and traffic policy, newest first

    endpoints.list

  • UpdateWrite

    Change an endpoint’s description, metadata, traffic policy or bindings, leaving fields that are omitted alone

    endpoints.update

Events

  • CreateWrite

    Subscribe to event types and deliver them to existing destination ids, which are created through a separate API

    events.create

  • DeleteDestructive

    Delete an event subscription, which stops those events being delivered

    events.delete

Connect ngrok to Claude, ChatGPT or Cursor

  1. 1

    Connect ngrok in Corsair

    Add your ngrok API key once in Corsair. Corsair stores the credential encrypted and makes the ngrok API calls for your agent, so it never goes into a prompt or a config file. Connect ngrok

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs ngrok. On a ChatGPT personal plan, connect ngrok here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, ngrok's read and write operations run right away and its 4 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/ngrok, add the ngrok plugin, and connect with an API key. Then call methods like corsair.ngrok.api.apiKeys.create() from your app. Corsair keeps each tenant isolated.

Yes. ngrok requires an API key from your ngrok account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit ngrok, GitHub, Notion, Stripe, and the rest. Trigger ngrok from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage ngrok cloud endpoints and their traffic policies, reserve custom domains, list agent tunnels and API keys, and manage event subscriptions that deliver ngrok events to your destinations. Common builds include sync jobs, admin tooling, and agents that call ngrok APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per ngrok API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/ngrok in the open repo. When ngrok ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your ngrok data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store ngrok data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put ngrok on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 4 destructive ngrok operations. You can change a link's mode at hub.corsair.dev/me.