Ngrok for AI agents
Ngrok creates secure tunnels to locally hosted applications, enabling developers to share and test webhooks or services without complex network configuration. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Ngrok.
Check an endpoint's configuration
Look up an endpoint's current settings before debugging a tunnel issue, read-only.
Create a tunnel credential
Create a new credential so a local service can establish a secure tunnel.
Approve before deleting an edge
Require approval before deleting an HTTPS edge, since it would take down any routes built on it.
102 Ngrok actions, graded by risk.
Every Ngrok action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
56Look things up. Allowed by default.
- ngrok.get_vaultGet Vault
- ngrok.get_secretGet Secret
- ngrok.get_api_keyGet API Key
- ngrok.list_vaultsList Vaults
- ngrok.get_endpointGet Endpoint
- ngrok.list_tunnelsList Active Tunnels
- ngrok.list_api_keysList API Keys
- ngrok.get_https_edgeGet HTTPS Edge
- ngrok.list_bot_usersList Bot Users
- ngrok.list_endpointsList All Endpoints
- ngrok.list_tcp_edgesList TCP Edges
- ngrok.list_tls_edgesList TLS Edges
- ngrok.get_credentialsGet Credentials
- ngrok.get_event_sourceGet Event Source
- ngrok.list_credentialsList Tunnel Credentials
- ngrok.list_https_edgesList HTTPS Edges
write
26Create and change things. Allow, or ask the user first.
- ngrok.create_vaultCreate Vault
- ngrok.update_vaultUpdate Vault
- ngrok.update_secretUpdate Secret
- ngrok.create_api_keyCreate API Key
- ngrok.update_api_keyUpdate API Key
- ngrok.create_endpointCreate Endpoint
- ngrok.update_endpointUpdate Endpoint
- ngrok.create_credentialCreate Tunnel Credential
- ngrok.create_https_edgeCreate HTTPS Edge
- ngrok.update_credentialsUpdate Credentials
- ngrok.create_event_sourceCreate Event Source
- ngrok.create_vault_secretCreate Vault Secret
- ngrok.create_ssh_credentialCreate SSH Credential
- ngrok.update_ssh_credentialUpdate SSH Credential
- ngrok.update_reserved_domainUpdate Reserved Domain
- ngrok.create_https_edge_routeCreate HTTPS Edge Route
destructive
20Delete, cancel or archive. Ask first, or deny outright.
- ngrok.delete_vaultDelete Vault
- ngrok.delete_secretDelete Secret
- ngrok.delete_api_keyDelete API Key
- ngrok.delete_endpointDelete Endpoint
- ngrok.delete_https_edgeDelete HTTPS Edge
- ngrok.delete_credentialsDelete Credentials
- ngrok.delete_event_sourceDelete Event Source
- ngrok.delete_ssh_credentialsDelete SSH Credentials
- ngrok.delete_https_edge_routeDelete HTTPS Edge Route
- ngrok.delete_event_subscriptionDelete Event Subscription
- ngrok.delete_edge_route_saml_moduleDelete Edge Route SAML Module
- ngrok.delete_reserved_domain_certificateDelete Reserved Domain Certificate
- ngrok.delete_edge_route_compression_moduleDelete Edge Route Compression Module
- ngrok.delete_edge_route_circuit_breaker_moduleDelete HTTPS Edge Route Circuit Breaker Module
- ngrok.delete_edge_route_request_headers_moduleDelete Edge Route Request Headers Module
- ngrok.delete_edge_route_response_headers_moduleDelete Edge Route Response Headers Module
Ngrok in three steps.
- 01Your users connect NgrokThey add their Ngrok api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Vault” can wait for the user, and “delete Vault” can be denied outright.
- 03Any agent can actYour agent calls Ngrok through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ngrok', { read: 'allow', write: 'ask', // create_vault destructive: 'deny', // delete_vault }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Ngrok connects.
Users add their Ngrok api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Ngrok connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Ngrok from any agent.
Ngrok and Arc0, answered.
Can I use Ngrok with Claude, ChatGPT or Cursor?
Yes. Connect Ngrok to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Ngrok actions you allow.
How do users connect Ngrok?
Users add their Ngrok api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Ngrok actions can my agent take?
102 in total: 56 read, 26 write and 20 destructive, such as “create Vault”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Ngrok?
Yes. Actions like “delete Vault” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Ngrok too?
Yes. The same Ngrok connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Ngrok into your agent.
Your users connect Ngrok once, under your brand. Your agent gets 102 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan