SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Hotspotsystem MCP with LangChain

Connect LangChain to Hotspotsystem MCP. List all customers at main street location, generate a single-use voucher for lobby, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Hotspotsystem logoHotspotsystem
Api Key

Hotspotsystem is a cloud-based platform for managing public Wi-Fi hotspots and guest access. It lets businesses automate user onboarding, track activity, and handle billing with ease.

19 Tools

Introduction

This guide walks you through connecting Hotspotsystem to LangChain using the Composio tool router. By the end, you'll have a working Hotspotsystem agent that can list Wi-Fi locations and customers, generate vouchers, track paid and social transactions, and list subscribers through natural language commands.

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

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

Also integrate Hotspotsystem with

Claude CodeClaude CoworkOpenAI Agents SDKClaude Agent SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Hotspotsystem project to Composio
  • Create a Tool Router MCP session for Hotspotsystem
  • Initialize an MCP client and retrieve Hotspotsystem tools
  • Build a LangChain agent that can interact with Hotspotsystem
  • 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 Hotspotsystem MCP server, and what's possible with it?

The Hotspotsystem MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Hotspotsystem account. It provides structured and secure access to your Wi-Fi hotspot management platform, so your agent can perform actions like listing customers, generating access vouchers, monitoring transactions, and managing subscribers across your locations.

  • Customer and subscriber management: Instantly list all customers or newsletter subscribers, or filter them by specific hotspot locations for targeted communications or support.
  • On-demand voucher generation: Have your agent create single-use access vouchers for guests or events—automatically and only when there are enough credits.
  • Location and asset visibility: Retrieve and review all your registered hotspot locations, making it easy to audit or manage distributed sites and devices.
  • Transaction monitoring and reporting: List MAC-based or paid transactions by location, enabling your agent to provide real-time analytics or billing support for your hotspots.
  • API health checks and diagnostics: Use the agent to ping the Hotspotsystem API for connectivity checks, ensuring your integrations and automations run smoothly.

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:

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

Step-by-step Guide

Step by step10 STEPS
1

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
2

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.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters 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/core is the core agent framework
  • dotenv/config loads environment variables
4

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
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Hotspotsystem functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
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 Hotspotsystem tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['hotspotsystem']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Hotspotsystem 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 Hotspotsystem tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "hotspotsystem-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Hotspotsystem MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Hotspotsystem tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

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

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept 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 invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

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

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['hotspotsystem']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "hotspotsystem-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Hotspotsystem related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Hotspotsystem 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.
TOOLS

Supported Tools

Every Hotspotsystem action and event your agent gets out of the box.

List Customers

Lists all customers in the HotspotSystem account with optional filtering.

List Customers by Location

Lists customers associated with a specified HotspotSystem location.

Generate Voucher (v1)

Generates a single-use hotspot access voucher for a specified location using its available voucher credits.

Get Locations Options

Tool to get simplified list of locations as dropdown options.

Get Me

Tool to verify the resource owner's credentials and retrieve authenticated user information.

List Paid Transactions

Tool to list paid transactions globally across all locations.

List Locations

Lists the resource owner's locations with optional field selection, sorting and pagination.

Misc Ping

Tool to perform health check against the HotspotSystem API.

List Subscribers

Lists newsletter subscribers across locations with optional field selection, sorting and pagination.

List Subscribers by Location

Tool to list subscribers by location.

List MAC Transactions

Tool to list MAC-based transactions.

List MAC Transactions by Location

Lists MAC address authentication transactions for a specific location, with optional field selection, sorting and pagination.

List Paid Transactions by Location

Tool to list paid transactions by location.

List Social Transactions

Tool to list social transactions.

List Social Transactions by Location

Tool to list social transactions by location.

List Voucher Transactions

Tool to list voucher transactions globally across all locations.

List Voucher Transactions by Location

Lists voucher transaction records for a specific HotspotSystem location.

List Vouchers

Lists the resource owner's vouchers across locations.

Vouchers List by Location

Lists vouchers for a specific HotspotSystem location, with optional field selection, sorting, and pagination.

FRAMEWORKS

How to build Hotspotsystem MCP Agent with another framework

Claude Code logo

Claude Code

Use Hotspotsystem MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Hotspotsystem MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Hotspotsystem MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Hotspotsystem MCP with Claude Agent SDK

Grok Bot logo

Grok Bot

Use Hotspotsystem MCP with Grok Bot

Codex logo

Codex

Use Hotspotsystem MCP with Codex

OpenClaw logo

OpenClaw

Use Hotspotsystem MCP with OpenClaw

Hermes logo

Hermes

Use Hotspotsystem MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Hotspotsystem MCP with Atomic Agent

Google ADK logo

Google ADK

Use Hotspotsystem MCP with Google ADK

Vercel AI SDK logo

Vercel AI SDK

Use Hotspotsystem MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Hotspotsystem MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Hotspotsystem MCP with LlamaIndex

CrewAI logo

CrewAI

Use Hotspotsystem MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Hotspotsystem MCP with Pydantic AI

AutoGen logo

AutoGen

Use Hotspotsystem MCP with AutoGen

FAQ

Frequently asked questions

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

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 Hotspotsystem tools.

Yes, absolutely. You can configure which Hotspotsystem 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.

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 Hotspotsystem data and credentials are handled as safely as possible.

Start with Hotspotsystem.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Hotspotsystem tool your agent needs.Free to start.

Start building