ngrok MCP. Manage all tunnels, keys, and security rules in conversation.
ngrok MCP gives you full command over your ingress infrastructure right from your AI agent. List active endpoints, check custom reserved domains, and audit security policies—all without leaving your chat window or terminal. Manage API keys and IP restrictions to secure network access and simplify complex tunneling setups.
Give Claude and any AI agent real-world access
List temporary tunnels and permanent edge routes used by your application.
Review current IP policies and restrictions applied to your ngrok account.
Retrieve a list of all reserved, custom domains associated with your applications.
List and manage the API keys used to authenticate access to your infrastructure.
Ask an AI about this
Waiting for input…
What AI agents can do with ngrok: 7 Tools for Ingress Management
These seven tools give you granular control over every aspect of your ngrok account, allowing your agent to list everything from public tunnels to IP restrictions.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using ngrok MCPList Api Keys
Retrieves a list of ngrok API keys used for authentication across the account.
List Endpoints
Gets a comprehensive list of all active public URLs (tunnels) configured in the...
List Https Edges
Lists advanced HTTPS edge configurations and their associated routing rules.
List Ip Policies
Shows all IP policies currently configured, detailing access controls by IP range.
List Ip Restrictions
Lists specific IP restrictions applied to the account dashboard and API access.
List Reserved Domains
Retrieves all custom domains that have been reserved for future use in applications.
List Vaults
Lists the secure vaults used to store sensitive values and credentials.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with ngrok, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ngrok. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Keeping track of public tunnels and security policies is a nightmare.
Every time a new microservice goes live, someone has to copy URLs from one dashboard into another, verify API keys in a separate vault, and then check the IP policy console just to make sure it's pointing to the right place. It’s constant tab switching and manual comparison.
With this MCP, you simply ask your agent what needs checking. Your AI client pulls together all active endpoints, reserved domains, and security rules into one readable summary. You get a single source of truth without ever leaving the chat.
ngrok MCP: Control your network access from natural conversation.
The need to switch between endpoint lists, policy screens, and key management portals disappears. You don't copy; you ask.
Now, whether you're checking `list_endpoints` or auditing `list_ip_policies`, the information flows directly into your workflow via chat. It’s instant visibility, every time.
What ngrok MCP does for your AI
Connecting ngrok to any AI client lets you take full control of your entire ingress infrastructure using natural conversation. Instead of navigating separate dashboards, your agent handles the heavy lifting. You can ask it to list all active public URLs—whether they're temporary tunnels or advanced edge routes. Need to check if a specific IP address is restricted? Ask about the current policies and restrictions.
You also get visibility into reserved domains and API keys across your account vault. It’s like getting a complete, real-time view of every tunnel and security setting without ever leaving your chat interface. This capability fits right in with Vinkius, making it easier to manage network complexity alongside all the other tools you rely on.
019e38c8-100d-7292-8c12-90cd5207bc74 How to set up ngrok MCP
The bottom line is that you get full visibility into your complex tunneling setup through simple chat prompts.
Subscribe to this MCP and enter your ngrok API Key.
Talk naturally with your AI client, telling it what network information you need (e.g., 'Show me all active endpoints').
Your agent executes the necessary commands and returns a clean summary of your infrastructure status.
Who uses ngrok MCP
This MCP is built for engineers who manage microservices, DevOps teams needing constant infrastructure oversight, and security specialists who can't rely on outdated dashboards. If you spend time clicking between a console, an API portal, and a dashboard just to check status, this is for you.
Auditing active endpoints and security policies across multiple environments in real-time.
Checking reserved domains and HTTPS edge configurations when developing locally against a staging environment.
Monitoring IP restrictions and vault usage to ensure compliance and maintain secure access boundaries.
Benefits of connecting ngrok MCP
Audit endpoints and policies instantly. Instead of logging into separate consoles to check active public URLs or IP restrictions, you ask your AI client directly for the status.
Keep track of custom domains easily. If you need to confirm if 'api.myapp.com' is reserved for a new project, just prompt the MCP instead of digging through domain management panels.
Centralize credential checks. You can list all necessary API keys and check secure vaults from one place, reducing the risk of using outdated or forgotten credentials.
Understand edge routing configurations. This tool lets you inspect detailed HTTPS edges, which is critical for advanced microservice deployments that require specific URL handling.
Secure access control review. Quickly verify IP policies and restrictions to ensure your network maintains compliance before a deployment goes live.
ngrok MCP use cases
Debugging an intermittent public connection
A developer notices a service is intermittently failing in production. They ask their agent, 'What are the active endpoints and current IP restrictions?' The MCP immediately lists all tunnels and confirms that no external IPs are currently restricted, pointing them to a firewall issue.
Preparing for an environment migration
A DevOps engineer is moving from staging to production. They prompt the agent to 'List reserved domains' to confirm all necessary custom names are secured, followed by checking 'list_api_keys' to ensure credentials haven't expired.
Onboarding a new security team member
A security analyst needs to understand the current threat surface. They ask the agent to check both 'list_ip_policies' and 'list_vaults' simultaneously, getting an immediate overview of all access rules and stored secrets.
Verifying a new service setup
A backend developer has finished building a local microservice. They ask the MCP to list HTTPS edges and check for available reserved domains, allowing them to provision a secure public URL without manual steps.
ngrok MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Checking status across multiple consoles
The developer manually opens three tabs: the ngrok dashboard, the API key management page, and the IP policy screen. They spend 15 minutes copying and pasting data to confirm nothing is wrong.
Connect this MCP. Ask your agent once: 'Show me all active endpoints, reserved domains, and current IP policies.' The AI client gathers all three pieces of information instantly.
Forgetting which credentials are needed
A developer tries to connect a new service but fails because they don't know if the primary API key is expired or restricted. They waste time contacting support.
Use the list_api_keys tool through your agent. It pulls the current credential status and shows you exactly what keys are active, preventing downtime.
Misconfiguring access rules
The security team applies a new IP restriction rule but forgets to verify if it impacts existing production tunnels or reserved domains.
Use the agent to check both list_ip_restrictions and list_reserved_domains. You confirm that your critical assets are unaffected by the new policy before activating it.
When to use ngrok MCP
Use this MCP if you need a single conversation interface to audit network infrastructure. This is for checking status, listing resources (like endpoints or domains), and verifying policies—it's about visibility and auditing. Don't use this if your goal is to actually modify the underlying configuration through code; while it gives you data points, direct API calls are still needed for complex creation/deletion tasks.
If your core task involves generating boilerplate infrastructure code (e.g., Terraform or CloudFormation), you might need a dedicated Infrastructure-as-Code MCP instead. But if the job is simply 'What do I have?'—then this MCP, leveraging tools like list_endpoints and list_ip_policies, gives you the immediate answers.
Frequently asked questions about ngrok MCP
How do I use ngrok MCP to check my active tunnels? +
Use the list_endpoints tool through your agent. It pulls a real-time list of all public URLs, letting you see which tunnels are currently running and visible.
Can I use ngrok MCP to check if my custom domain is reserved? +
Yes, prompt the agent about 'reserved domains.' It uses list_reserved_domains to show all custom names you've set aside for future projects.
What does ngrok MCP use to manage credentials? +
The MCP interacts with your account vault, allowing you to list and audit API keys using the list_api_keys tool. This keeps sensitive values managed and visible to your agent.
Is ngrok MCP only for checking endpoints? +
No. It handles security too. You can use list_ip_policies and list_ip_restrictions to verify access controls, not just the public URLs themselves.
Does ngrok MCP help with HTTPS edge configurations? +
Yes. You can specifically ask about advanced routing using the list_https_edges tool, giving you insight into complex URL handling rules.