Compatible with every major AI agent and IDE
What is the ngrok MCP Server?
Connect your ngrok account to any AI agent and take full control of your ingress infrastructure through natural conversation.
What you can do
- Endpoints & Edges — List all active public URLs (ephemeral, edge, or cloud) and inspect HTTPS edges for advanced routing configurations
- Security & Access — Audit IP policies and restrictions applied to your dashboard, API, or agents to ensure secure access
- Domain Management — Retrieve all custom domains reserved for your applications directly from the ngrok cloud
- Credential Management — List API keys used for authentication and manage secure vaults for sensitive values
- Infrastructure Visibility — Get a bird's-eye view of your entire tunneling setup without leaving your terminal or chat interface
How it works
- Subscribe to this server
- Enter your ngrok API Key
- Start managing your tunnels and security from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — quickly audit active endpoints and security policies across the organization
- Backend Developers — check reserved domains and HTTPS edge configurations during local development
- Security Teams — monitor IP restrictions and vault usage to maintain compliance and secure access
Built-in capabilities (7)
List ngrok API keys
List ngrok endpoints
List ngrok HTTPS edges
List ngrok IP policies
List ngrok IP restrictions
List ngrok reserved domains
List ngrok vaults
Why Claude Code?
Claude Code registers ngrok as an MCP server in a single terminal command. Once connected, Claude Code discovers all 7 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where ngrok data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using ngrok tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
ngrok in Claude Code
ngrok and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ngrok to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for ngrok in Claude Code
The ngrok MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 7 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
ngrok for Claude Code
Every tool call from Claude Code to the ngrok MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see all my active public URLs currently served by ngrok?
Yes! Use the list_endpoints tool to retrieve all public URLs, whether they are ephemeral, edge-based, or cloud endpoints.
How do I check which custom domains I have reserved?
Simply ask the agent to run the list_reserved_domains action. It will return a list of all custom domains configured in your ngrok account.
Is it possible to audit my IP security policies?
Yes. You can use list_ip_policies and list_ip_restrictions to review the access control rules applied to your infrastructure.
How do I add an MCP server to Claude Code?
Run claude mcp add <name> --transport http "<url>" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable
Explore More MCP Servers
View all →
CockroachDB Cloud
8 toolsManage distributed SQL clusters via CockroachDB Cloud — track clusters, monitor nodes, and audit network allowlists directly from any AI agent.

Fulcrum
10 toolsManage field data collection, track form records, and query datasets via AI agents with Fulcrum.

Fintoc
12 toolsAccess bank accounts, movements, and initiate transfers via AI agents with Fintoc.

Zinrelo
9 toolsManage loyalty programs, reward points, and customer engagement via the Zinrelo API.
