How to connect Ngrok to OpenClaw
Connect Ngrok to OpenClaw with ClawLink: paste your Ngrok key once and 102 tools work from chat. No MCP server to run, nothing stored on your machine.
NgrokAPI KEYMCPNgrok creates secure tunnels to locally hosted applications, enabling developers to share and test webhooks or services without configuring complex network settings.. Once connected, OpenClaw can read and act on Ngrok from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Ngrok access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Ngrok setup: install one ClawHub skill, connect Ngrok in the browser, and OpenClaw can call real Ngrok actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into OpenClaw, or open the Ngrok skill on ClawHub.
Before installing anything, inspect the ClawHub skill metadata and setup requirements.
If the skill asks you to install a third-party package or CLI, verify its source, maintainer, and package contents before running the install command.
Install the skill "Ngrok" (hith3sh/ngrok-workspace) from ClawHub only after those checks pass.
Skill page: https://clawhub.ai/hith3sh/ngrok-workspace
Keep the work scoped to this skill only.
After install, help me finish setup from verified skill metadata.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.Setup
It takes three steps to connect OpenClaw to Ngrok.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Ngrok
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Ngrok?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Ngrok in the ClawLink dashboard — paste your Ngrok API key once.
Verify the connection by asking OpenClaw:
Create it in Ngrok for me, then confirm the important fields before you finish.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Ngrok is connected in the dashboard, that agent calls the same 102 Ngrok tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Ngrok MCP for OpenClaw
Looking for a Ngrok MCP server for OpenClaw? ClawLink connects Ngrok to OpenClaw and exposes 102 Ngrok tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Ngrok integration works the same way.
What the OpenClaw Ngrok integration can do
102 Ngrok tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 102.
30 of 102 Ngrok tools for OpenClaw
| Tool | What it does |
|---|---|
Create API key ngrok_create_api_key | Creates a new API key for authenticating with the ngrok API |
Create credential ngrok_create_credential | Creates a new tunnel authtoken credential for authenticating ngrok agents |
Create endpoint ngrok_create_endpoint | Create a cloud endpoint on the ngrok account |
Create event source ngrok_create_event_source | Add a new event source to an event subscription |
Get API key ngrok_get_api_key | Get the details of an API key by ID |
Get credentials ngrok_get_credentials | Retrieve detailed information about a tunnel authtoken credential by ID |
Get edge route backend module ngrok_get_edge_route_backend_module | Retrieves the backend module configuration for an HTTPS edge route |
Get edge route circuit breaker module ngrok_get_edge_route_circuit_breaker_module | Retrieve the circuit breaker module configuration for a specific HTTPS edge route |
Get edge route compression module ngrok_get_edge_route_compression_module | Retrieves the compression module configuration for a specific HTTPS edge route |
Get edge route ip restriction module ngrok_get_edge_route_ip_restriction_module | Retrieves the IP restriction module configuration for a specific HTTPS edge route |
Get edge route oidc module ngrok_get_edge_route_oidc_module | Retrieves the OIDC (OpenID Connect) module configuration for a specific HTTPS edge route |
Get edge route request headers module ngrok_get_edge_route_request_headers_module | Retrieves the request headers module configuration for a specific HTTPS edge route |
Get edge route response headers module ngrok_get_edge_route_response_headers_module | Get the response headers module configuration for an HTTPS edge route |
Get edge route saml module ngrok_get_edge_route_saml_module | Retrieves the SAML authentication module configuration for a specific HTTPS edge route |
Get edge route traffic policy ngrok_get_edge_route_traffic_policy | Retrieves the Traffic Policy module configuration for a specific HTTPS edge route |
Get edge route user agent filter module ngrok_get_edge_route_user_agent_filter_module | Retrieves the user agent filter module configuration for a specific HTTPS edge route |
Get edge route webhook verification module ngrok_get_edge_route_webhook_verification_module | Retrieves the webhook verification module configuration for an HTTPS edge route |
Get edge route websocket tcp converter module ngrok_get_edge_route_websocket_tcp_converter_module | Retrieves the WebSocket TCP Converter module configuration for a specific HTTPS edge route |
Get endpoint ngrok_get_endpoint | Get the status of an endpoint by ID |
Get event source ngrok_get_event_source | Get an event source by type for a specific event subscription |
Get https edge ngrok_get_https_edge | Get the details of an HTTPS edge by ID |
Get https edge mutual tls module ngrok_get_https_edge_mutual_tls_module | Retrieves the mutual TLS module configuration for an HTTPS edge |
Get https edge route ngrok_get_https_edge_route | Retrieves detailed information about a specific HTTPS edge route by its ID |
Get ip restrictions ngrok_get_ip_restrictions | Retrieves detailed information about a specific IP restriction by its ID |
Get reserved domain ngrok_get_reserved_domain | Get the details of a reserved domain by ID |
Get secret ngrok_get_secret | Retrieve detailed information about a vault secret by ID |
Get secrets by vault ngrok_get_secrets_by_vault | Get all secrets in a vault by vault ID |
Get ssh credentials ngrok_get_ssh_credentials | Retrieve detailed information about an SSH credential by ID |
Get vault ngrok_get_vault | Get the details of a vault by ID |
List agent ingresses ngrok_list_agent_ingresses | List all Agent Ingresses owned by this account |
Try it: find the Ngrok tool you need
Browse the 30 Ngrok tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Ngrok for me, then confirm the important fields before you finish.
Create it in Ngrok for me, then confirm the important fields before you finish.
Create it in Ngrok for me, then confirm the important fields before you finish.
Create it in Ngrok for me, then confirm the important fields before you finish.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Ngrok working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Ngrok API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ngrok account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Ngrok. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Ngrok actions to the runtime in a format your agent can reliably use. | 102 tools for Ngrok are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Ngrok to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Ngrok in the browser, and the 102 tools above work from chat. There is no SDK and no config file, and the Ngrok key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Ngrok skill but can't call the tools
The ClawHub skill teaches OpenClaw about Ngrok, but the calls run through the ClawLink plugin and your connected account. Make sure Ngrok is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Ngrok from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Ngrok tools
Ngrok tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Ngrok call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Ngrok returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Ngrok has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Ngrok integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Ngrok: link your Ngrok account once in the browser and OpenClaw can call the Ngrok API through 102 ready-made tools — no custom code or token handling.
How do I add Ngrok to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Ngrok skill from ClawHub, then you click Connect in the dashboard to authorize Ngrok. OpenClaw calls the tools from the next message — no config files, and the Ngrok key you paste is stored server-side instead of in your environment.
How long does it take to connect Ngrok to OpenClaw?
About two minutes. Sign in, click Connect next to Ngrok in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Ngrok up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Ngrok working from chat.
OpenClaw installed the Ngrok skill but can't call the tools
The ClawHub skill teaches OpenClaw about Ngrok, but the calls run through the ClawLink plugin and your connected account. Make sure Ngrok is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
GitHub
Manage repositories, issues, pull requests, and workflows
OpenClaw PagerDuty integration
Manage incidents, on-call schedules, and services
OpenClaw SafetyCulture integration
SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.