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 Cursor?
Cursor's Agent mode turns ngrok into an in-editor superpower. Ask Cursor to generate code using live data from ngrok and it fetches, processes, and writes. all in a single agentic loop. 7 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
ngrok in Cursor
ngrok and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ngrok to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Sellsy
12 toolsEquip your AI agent with full read access to your Sellsy CRM to audit deals, generate invoices overviews, and prospect natively.

Kylas
7 toolsScale your Indian SMB sales team with a CRM that combines lead management, pipeline tracking, and WhatsApp integration natively.

Hudu
10 toolsManage IT documentation, assets, and passwords via Hudu API.

edX
8 toolsSearch and discover online courses from Harvard, MIT, Berkeley and 160+ top institutions on edX.
