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 Desktop?
Claude Desktop is the definitive way to connect ngrok to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 7 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
ngrok in Claude Desktop
ngrok and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ngrok to Claude Desktop 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 Desktop
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 Desktop 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 Desktop
Every tool call from Claude Desktop 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 does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
DNSimple
77 toolsManage domains, DNSSEC, and email forwarding via DNSimple — list accounts, control domains, and manage DS records directly from your AI agent.

Google Calendar
12 toolsSync and orchestrate your agenda securely — scan, schedule, and manipulate Google Calendar events natively in chat.

DoiT
10 toolsEquip your AI agent to manage cloud costs, track assets across AWS/GCP/Azure, and monitor cost anomalies via the DoiT API.

Donately
10 toolsEquip your AI agent to manage donations, track donors, and monitor fundraising campaigns via the Donately API.
