Try it now
Name a service in the second prompt to choose which one the AI agent looks at. In the third, ask for any response acustom-response action can send, such as JSON or an HTML page.
To keep changing that page, see Build a page, then change it.
Understand what’s running
These prompts cover what’s connected right now, plus your reserved domains and certificates. Swap in the error code you got. If the ngrok error page also shows a request ID, paste both.Analyze traffic
These prompts read Traffic Inspector, including TCP connections. How far back your AI agent can look depends on your plan’s retention. Narrow any prompt to a host, path, status code, method, or client IP, and ask for counts by hour, by day, or by country.Create traffic rules
The AI agent writes Traffic Policy, checks it with the validator, and saves it to a Cloud Endpoint. The MCP server can’t write to your ngrok agent’s config file, but a coding agent can edit that file itself. Swap in your own paths, limits, and countries, or another OAuth provider, such as GitHub or Microsoft. See Traffic Policy actions for everything a rule can do.Set up endpoints and resources
The AI agent can create and change Cloud Endpoints, reserved domains, TCP addresses, vaults, and secrets. Swap in your own domain, and name the service or vault you mean. It asks before it deletes anything, and it can confirm that a secret exists but can’t read it back.Check your account
Change the time window, or ask about authtokens, SSH keys, or personal access tokens instead of API keys. The AI agent sees each credential’s description, owner, and dates, but never the key or token itself.Send feedback
The AI agent sends feedback about the MCP server’s tools to the ngrok team. In the second prompt, replace<YOUR_IDEA_HERE> with your idea.