Ngrok with LangChain

How to integrate Ngrok MCP with LangChain

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Ngrok with TL;DR What is LangChain What is the Ngrok MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Ngrok MCP Agent with another framework Explore Other Toolkits FAQ

Connect Ngrok without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Ngrok to LangChain using the Composio tool router. By the end, you'll have a working Ngrok agent that can list all active tunnels and endpoints, show https edges currently configured, list all api keys for your account through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Ngrok account through Composio's Ngrok MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Ngrok with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your OpenAI and Composio API keys
Connect your Ngrok project to Composio
Create a Tool Router MCP session for Ngrok
Initialize an MCP client and retrieve Ngrok tools
Build a LangChain agent that can interact with Ngrok
Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

Agent Framework: Build agents that can use tools and make decisions
MCP Integration: Connect to external services through Model Context Protocol adapters
Memory Management: Maintain conversation history across interactions
Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

What is the Ngrok MCP server, and what's possible with it?

The Ngrok MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ngrok account. It provides structured and secure access to your Ngrok tunnels and API keys, so your agent can perform actions like managing endpoints, listing tunnels, handling API keys, and auditing IP restrictions on your behalf.

Active tunnel and endpoint monitoring: Instantly list all active tunnels and endpoints in your Ngrok account, making it simple to track running services and public URLs.
API key management: Programmatically create, list, and delete API keys to securely manage who and what can access your Ngrok resources.
HTTPS edge configuration visibility: Retrieve a comprehensive list of all HTTPS edges to review and manage how Ngrok handles encrypted traffic.
IP restriction and policy auditing: List and inspect all IP restrictions and policy rules, helping you enforce access control and security best practices.
Detailed access audit trails: Fetch details about specific IP restrictions for security audits and compliance, ensuring you always know who can access your tunnels and APIs.

Supported Tools & Triggers

Tools

Create API KeyCreates a new API key for authenticating with the ngrok API.

Create Tunnel CredentialCreates a new tunnel authtoken credential for authenticating ngrok agents.

Create EndpointCreate a cloud endpoint on the ngrok account.

Create Event SourceAdd a new event source to an event subscription.

Create Event SubscriptionCreates a new event subscription in ngrok.

Create HTTPS EdgeCreates a new HTTPS edge in your ngrok account.

Create HTTPS Edge RouteCreates a new route on an HTTPS edge in ngrok.

Create SSH CredentialCreates a new SSH credential from an uploaded public SSH key.

Create VaultCreates a new vault in your ngrok account.

Create Vault SecretTool to create a new secret in an ngrok vault for secure storage of sensitive data like API keys, passwords, or tokens.

Delete API KeyDelete an API key by its ID.

Delete CredentialsDelete a tunnel authtoken credential by ID.

Delete HTTPS Edge Route Circuit Breaker ModuleDelete the Circuit Breaker module from an HTTPS Edge Route.

Delete Edge Route Compression ModuleDelete the compression module from an HTTPS edge route.

Delete Edge Route Request Headers ModuleDelete the request headers module from an HTTPS edge route.

Delete Edge Route Response Headers ModuleDelete the response headers module from an HTTPS edge route.

Delete Edge Route SAML ModuleDelete the SAML module configuration from an HTTPS edge route.

Delete Edge Route User Agent Filter ModuleDelete the user agent filter module from an HTTPS edge route.

Delete Edge Route Webhook Verification ModuleDelete the webhook verification module from an HTTPS edge route.

Delete Edge Route WebSocket TCP Converter ModuleDelete the WebSocket TCP converter module from an HTTPS edge route.

Delete EndpointDelete an endpoint by ID.

Delete Event SourceDelete an event source from an event subscription.

Delete Event SubscriptionDelete an event subscription by ID.

Delete HTTPS EdgeDelete an HTTPS edge by ID.

Delete HTTPS Edge RouteDelete an HTTPS edge route by ID.

Delete Reserved Domain CertificateDetach the certificate attached to a reserved domain.

Delete Reserved Domain Certificate Management PolicyDetach the certificate management policy from a reserved domain.

Delete SecretDelete a vault secret by ID.

Delete SSH CredentialsDelete an SSH credential by ID.

Delete VaultDelete a vault by ID.

Get API KeyGet the details of an API key by ID.

Get CredentialsTool to retrieve detailed information about a tunnel authtoken credential by ID.

Get Edge Route Backend ModuleRetrieves the backend module configuration for an HTTPS edge route.

Get Edge Route Circuit Breaker ModuleTool to retrieve the circuit breaker module configuration for a specific HTTPS edge route.

Get Edge Route Compression ModuleRetrieves the compression module configuration for a specific HTTPS edge route.

Get Edge Route IP Restriction ModuleRetrieves the IP restriction module configuration for a specific HTTPS edge route.

Get Edge Route OIDC ModuleRetrieves the OIDC (OpenID Connect) module configuration for a specific HTTPS edge route.

Get Edge Route Request Headers ModuleRetrieves the request headers module configuration for a specific HTTPS edge route.

Get Edge Route Response Headers ModuleGet the response headers module configuration for an HTTPS edge route.

Get Edge Route SAML ModuleRetrieves the SAML authentication module configuration for a specific HTTPS edge route.

Get Edge Route Traffic PolicyRetrieves the Traffic Policy module configuration for a specific HTTPS edge route.

Get Edge Route User Agent Filter ModuleRetrieves the user agent filter module configuration for a specific HTTPS edge route.

Get Edge Route Webhook Verification ModuleRetrieves the webhook verification module configuration for an HTTPS edge route.

Get Edge Route WebSocket TCP Converter ModuleRetrieves the WebSocket TCP Converter module configuration for a specific HTTPS edge route.

Get EndpointGet the status of an endpoint by ID.

Get Event SourceGet an event source by type for a specific event subscription.

Get HTTPS EdgeGet the details of an HTTPS edge by ID.

Get HTTPS Edge Mutual TLS ModuleRetrieves the mutual TLS module configuration for an HTTPS edge.

Get HTTPS Edge RouteRetrieves detailed information about a specific HTTPS edge route by its ID.

Get IP Restriction DetailsRetrieves detailed information about a specific IP restriction by its ID.

Get Reserved DomainGet the details of a reserved domain by ID.

Get SecretTool to retrieve detailed information about a vault secret by ID.

Get Secrets by VaultTool to get all secrets in a vault by vault ID.

Get SSH CredentialsTool to retrieve detailed information about an SSH credential by ID.

Get VaultGet the details of a vault by ID.

List Agent IngressesList all Agent Ingresses owned by this account.

List API KeysThis tool lists all API keys owned by the user.

List Bot UsersTool to list all bot users on this ngrok account.

List Certificate AuthoritiesList all certificate authorities on this account.

List Tunnel CredentialsList all tunnel authtoken credentials on the ngrok account.

List All EndpointsList all active endpoints on the ngrok account.

List Event DestinationsList all Event Destinations on the ngrok account.

List Event SubscriptionsList all event subscriptions on the ngrok account.

List Event Subscription SourcesTool to list the types for which this event subscription will trigger.

List Failover BackendsList all failover backends on this account.

List HTTP Response BackendsList all HTTP response backends on the account.

List HTTPS EdgesLists all HTTPS Edges in your ngrok account.

List IP PoliciesList all IP policies on this account.

List IP Policy RulesThis tool lists all IP policy rules associated with your ngrok account.

List IP RestrictionsLists all IP restrictions configured on the ngrok account.

List Reserved AddressesList all reserved addresses on this account.

List Reserved DomainsList all reserved domains on this account.

List Service UsersTool to list all service users on this ngrok account.

List SSH Certificate AuthoritiesList all SSH Certificate Authorities on this account.

List SSH CredentialsList all SSH credentials on the ngrok account.

List SSH Host CertificatesList all SSH Host Certificates issued on this account.

List SSH User CertificatesList all SSH user certificates on the ngrok account.

List Static BackendsList all static backends on the account.

List TCP EdgesLists all TCP Edges in your ngrok account.

List TLS CertificatesList all TLS certificates on the ngrok account.

List TLS EdgesLists all TLS Edges in your ngrok account.

List Active TunnelsList all active tunnels in the ngrok account.

List Tunnel SessionsList all online tunnel sessions running on this account.

List VaultsList all vaults owned by the ngrok account.

List Vault SecretsList all vault secrets owned by the ngrok account.

List Weighted BackendsList all weighted backends on the ngrok account.

Replace Edge Route Circuit Breaker ModuleReplaces the circuit breaker module configuration on an HTTPS edge route.

Replace Edge Route Compression ModuleReplaces the compression module configuration for an HTTPS edge route.

Replace Edge Route Request Headers ModuleReplaces the request headers module configuration for an HTTPS edge route.

Replace Edge Route Response Headers ModuleReplaces the response headers module configuration for an HTTPS edge route.

Replace Edge Route Traffic PolicyReplaces the traffic policy module on an HTTPS edge route.

Replace Edge Route User Agent Filter ModuleReplaces the user agent filter module configuration for an HTTPS edge route.

Replace Edge Route Webhook Verification ModuleReplaces the webhook verification module configuration for an HTTPS edge route.

Update API KeyUpdates attributes of an API key by ID.

Update CredentialsTool to update attributes of a tunnel authtoken credential by ID.

Update EndpointTool to update an Endpoint by ID, currently available only for cloud endpoints.

Update Event SubscriptionTool to update attributes of an event subscription by ID.

Update HTTPS Edge RouteTool to update an HTTPS edge route by ID.

Update Reserved DomainTool to update the attributes of a reserved domain by ID.

Update SecretTool to update a vault secret by ID.

Update SSH CredentialTool to update attributes of an SSH credential by ID.

Update VaultTool to update attributes of a vault by ID.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting this tutorial, make sure you have:

Python 3.10 or higher installed on your system
A Composio account with an API key
An OpenAI API key
Basic familiarity with Python and async programming

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-langchain langchain-mcp-adapters langchain python-dotenv

Install the required packages for LangChain with MCP support.

What's happening:

composio-langchain provides Composio integration for LangChain
langchain-mcp-adapters enables MCP client connections
langchain is the core agent framework
python-dotenv loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates your requests to Composio's API
COMPOSIO_USER_ID identifies the user for session management
OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

What's happening:

We're importing LangChain's MCP adapter and Composio SDK
The dotenv import loads environment variables from your .env file
This setup prepares the foundation for connecting LangChain with Ngrok functionality through MCP

Initialize Composio client

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")

What's happening:

We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
Creating a Composio instance that will manage our connection to Ngrok tools
Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

# Create Tool Router session for Ngrok
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['ngrok']
)

url = session.mcp.url

What's happening:

We're creating a Tool Router session that gives your agent access to Ngrok tools
The create method takes the user ID and specifies which toolkits should be available
The returned session.mcp.url is the MCP server URL that your agent will use
This approach allows the agent to dynamically load and use Ngrok tools as needed

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "ngrok-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)

What's happening:

We're creating a MultiServerMCPClient that connects to our Ngrok MCP server via HTTP
The client is configured with a name and the URL from our Tool Router session
get_tools() retrieves all available Ngrok tools that the agent can use
We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Ngrok related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")

What's happening:

We initialize an empty conversation_history list to maintain context across interactions
A while loop continuously accepts user input from the command line
When a user types a message, it's added to the conversation history and sent to the agent
The agent processes the request using the ainvoke() method with the full conversation history
Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

if __name__ == "__main__":
    asyncio.run(main())

What's happening:

We call the main() function using asyncio.run() to start the application

Complete Code

Here's the complete code to get you started with Ngrok and LangChain:

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['ngrok']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "ngrok-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Ngrok related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've successfully built a LangChain agent that can interact with Ngrok through Composio's Tool Router.

Key features of this implementation:

Dynamic tool loading through Composio's Tool Router
Conversation history maintenance for context-aware responses
Async Python provides clean, efficient execution of agent workflows

You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

How to build Ngrok MCP Agent with another framework

OpenAI Agents SDK

Use Ngrok MCP with OpenAI Agents SDK

Claude Agent SDK

Use Ngrok MCP with Claude Agent SDK

Claude Code

Use Ngrok MCP with Claude Code

Claude Cowork

Use Ngrok MCP with Claude Cowork

Codex

Use Ngrok MCP with Codex

OpenClaw

Use Ngrok MCP with OpenClaw

Hermes

Use Ngrok MCP with Hermes

CLI

Use Ngrok MCP with CLI

Google ADK

Use Ngrok MCP with Google ADK

Vercel AI SDK

Use Ngrok MCP with Vercel AI SDK

Mastra AI

Use Ngrok MCP with Mastra AI

LlamaIndex

Use Ngrok MCP with LlamaIndex

CrewAI

Use Ngrok MCP with CrewAI

Explore Other Toolkits

Supabase

Oauth2Api Key

Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.

Codeinterpreter

No Auth

Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.

GitHub

Oauth2

GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.

TOOLKIT MARKETPLACE

FAQ

What are the differences in Tool Router MCP and Ngrok MCP?

With a standalone Ngrok MCP server, the agents and LLMs can only access a fixed set of Ngrok tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ngrok and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with LangChain?

Yes, you can. LangChain fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Ngrok tools.

Can I manage the permissions and scopes for Ngrok while using Tool Router?

Yes, absolutely. You can configure which Ngrok scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Ngrok data and credentials are handled as safely as possible.

Used by agents from

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

How to integrate Ngrok MCP with LangChain

Table of Contents

Connect Ngrok without Auth hassles

Introduction

Also integrate Ngrok with

TL;DR

What is LangChain?

What is the Ngrok MCP server, and what's possible with it?

Supported Tools & Triggers

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies

Initialize Composio client

Create a Tool Router session

Configure the agent with the MCP URL

Set up interactive chat interface

Run the application

Complete Code

Conclusion

How to build Ngrok MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Supabase

Codeinterpreter

GitHub

FAQ

What are the differences in Tool Router MCP and Ngrok MCP?

Can I use Tool Router MCP with LangChain?

Can I manage the permissions and scopes for Ngrok while using Tool Router?

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability