Developer Tools & Devops · Ngrok + Claude
Ngrok MCP with Claude: Share and Test Local Apps Through Natural Language
The short answer
Claude works with Ngrok through the Model Context Protocol (MCP), an open standard that acts as a secure adapter between the two. Once connected with an API key, Claude can create tunnels, check active sessions and manage endpoints when a person asks in plain language, within permissions the organisation sets.
What is Ngrok?
Ngrok is a tunnelling service that makes a program running on a developer's laptop or server reachable over the internet, securely and without complex network setup. Developers use it to share work in progress, test applications with outside parties and receive webhooks from services such as payment or messaging platforms. It is widely used by software engineering, quality assurance and DevOps teams.
How Claude connects to Ngrok through MCP
The Model Context Protocol (MCP) is an open standard that lets Claude securely use other software, reading information and taking actions with permissions the organisation controls. Think of it as a universal adapter between Claude and a tool. For Ngrok, the connection can use the tool's own MCP server or a secure managed connector, so Claude works with your account in a defined way.
Once connected, Claude can typically look up active tunnels and sessions, open a new tunnel to a local port, review endpoints and explain what is running. A developer might simply ask for a shareable address for a local test build, and Claude handles the request. Access is limited to what the API key allows, so Claude cannot reach beyond the scope you set.
Permissions and approvals keep people in charge. Actions that change live exposure, such as opening a new public tunnel, can be set to require a named person's confirmation before they run. Every request and result is logged, so IT and security leaders can review who asked for what and when.
What you can automate
Instant sharing of work in progress
A designer or product manager asks Claude for a public link to the local build they are reviewing. Claude opens a tunnel to the correct port, confirms the address and shares it with the reviewer. When the review ends, the tunnel can be closed on request, so temporary access does not linger.
Monitoring active sessions
An operations lead asks which tunnels are running across the team. Claude lists active sessions, shows their age and purpose where tagged, and flags any that have been open longer than policy allows. This gives a clear picture without logging into the dashboard.
Webhook testing for integrations
A developer building a payment or order integration needs a live address to receive test callbacks. Claude sets up a tunnel to the local development server and reports the address. The developer can then watch incoming requests as the third-party service sends them.
Customer demonstrations
A sales engineer preparing a live demo for a prospect asks Claude to expose the demo environment for a fixed period. Claude creates the tunnel, notes when it should close and reminds the team. This keeps demonstrations smooth while limiting how long the environment is reachable.
Endpoint housekeeping
An IT or DevOps lead asks Claude to review endpoints that have not been used recently. Claude summarises them so the team can decide which to retire. Removal stays with a person, so nothing is deleted without sign-off.
An end-to-end workflow: Partner demo approval and access log
TriggerA sales lead requests a live demo environment for a partner meeting in a support ticket.
Claude reads the ticket and confirms the requested environment, duration and attendees.
Claude prepares a tunnel request and sends it to the IT lead for approval in the team's chat channel.
Once approved, Claude opens the tunnel to the demo port and records the address.
Claude posts the address and closing time to the ticket and the sales lead's calendar entry.
At the agreed time, Claude closes the tunnel and records the session in the access log held in the organisation's Microsoft 365 workspace.
Claude adds a short summary to the CRM opportunity record for the sales team.
OutcomeDemonstrations run on schedule with a clear approval trail, access is closed on time, and the sales team has a complete record for follow-up. Results will vary by team and setup.
How we set it up
Free automation audit
We review how your developers, QA and operations teams share and test local applications today, and identify the workflows worth automating. You leave with a clear plan and no obligation.
Secure API key connection
We connect Claude to Ngrok using an API key, scoped to the minimum access needed. Keys are stored in your secrets manager, never in shared documents, and can be rotated at any time.
Workflow design
We design the end-to-end workflow across Ngrok and your other systems, such as Microsoft 365, your CRM or your ticketing tool. People approve every action that changes live exposure.
Testing and launch
We test against real past cases, then launch with monitoring and audit logs turned on, so every tunnel opened and closed is recorded.
Team training
We train your developers, QA and operations staff on how to ask Claude for what they need and how approvals work, so the team can use the workflow confidently from day one.
Who benefits
- Software developers
- Get shareable test addresses and webhook endpoints by asking, instead of configuring networks by hand.
- QA and test leads
- Expose test builds to reviewers quickly and see which sessions are active at any moment.
- DevOps and IT leaders
- Keep oversight of live exposure through approvals, monitoring and audit logs.
- Sales and customer teams
- Run reliable live demonstrations with access that opens and closes on schedule.
Security and control
- Use an API key with the least access needed, and rotate it on a set schedule.
- Require named approval before any new public tunnel is opened.
- Set time limits on tunnels so temporary access closes automatically or on request.
- Keep audit logs of every request, action and result for review by IT and security.
- Store credentials in a secrets manager and never expose them to the model's chat history.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can host Claude in those regions to align with their data protection and security requirements. In India, we design workflows that respect the Digital Personal Data Protection Act, 2023, with hosting in India where needed. For organisations in the UAE and Saudi Arabia, we align with local data protection laws and select a hosting region that meets their requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Ngrok MCP server do?
The Ngrok MCP server lets Claude work with your Ngrok account through a defined, secure connection. Typically it allows Claude to create tunnels, see active sessions and manage endpoints when asked in plain language. It acts as a controlled bridge, so Claude only uses what the connection permits.
Is connecting Ngrok to Claude secure?
Security depends on how the connection is set up. We use an API key with minimal access, store it in a secrets manager, require approval for changes that expose local apps publicly and keep full audit logs. These measures reduce risk, but we cannot guarantee that no incident will occur, so we also review your wider security practices.
What can Claude do with Ngrok once connected?
Typically Claude can open tunnels to local ports, list running sessions, review endpoints and summarise what is active. It can also post results into your other tools, such as tickets or chat. Sensitive actions can require a person's confirmation before they run.
How long does setup take?
Timing depends on how many workflows you want and how many systems they touch. A focused setup for one team often takes a few weeks, including the free audit, testing and training. We will give you a realistic timeline after reviewing your needs.
What account access or permissions do I need?
You need an Ngrok API key from your account with permissions that match the actions you want Claude to take. We recommend a key with the least access required, ideally created for this purpose. Your plan and permission levels should be confirmed with Ngrok, and we will advise on the right scope during the audit.