# How to integrate Hotspotsystem MCP with CrewAI

```json
{
  "title": "How to integrate Hotspotsystem MCP with CrewAI",
  "toolkit": "Hotspotsystem",
  "toolkit_slug": "hotspotsystem",
  "framework": "CrewAI",
  "framework_slug": "crew-ai",
  "url": "https://composio.dev/toolkits/hotspotsystem/framework/crew-ai",
  "markdown_url": "https://composio.dev/toolkits/hotspotsystem/framework/crew-ai.md",
  "updated_at": "2026-05-12T10:15:08.718Z"
}
```

## Introduction

This guide walks you through connecting Hotspotsystem to CrewAI using the Composio tool router. By the end, you'll have a working Hotspotsystem agent that can list all customers at main street location, generate a single-use voucher for lobby, list paid transactions for downtown hotspot through natural language commands.
This guide will help you understand how to give your CrewAI 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

- [OpenAI Agents SDK](https://composio.dev/toolkits/hotspotsystem/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/hotspotsystem/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/hotspotsystem/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/hotspotsystem/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/hotspotsystem/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/hotspotsystem/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/hotspotsystem/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/hotspotsystem/framework/cli)
- [Google ADK](https://composio.dev/toolkits/hotspotsystem/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/hotspotsystem/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/hotspotsystem/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/hotspotsystem/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/hotspotsystem/framework/llama-index)

## TL;DR

Here's what you'll learn:
- Get a Composio API key and configure your Hotspotsystem connection
- Set up CrewAI with an MCP enabled agent
- Create a Tool Router session or standalone MCP server for Hotspotsystem
- Build a conversational loop where your agent can execute Hotspotsystem operations

## What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.
Key features include:
- Agent Roles: Define specialized agents with specific goals and backstories
- Task Management: Create tasks with clear descriptions and expected outputs
- Crew Orchestration: Combine agents and tasks into collaborative workflows
- MCP Integration: Connect to external tools through Model Context Protocol

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

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `HOTSPOTSYSTEM_CUSTOMERS_LIST` | List Customers | Lists all customers in the HotspotSystem account with optional filtering. Use this tool to: - Retrieve all customers with their details (name, email, contact info, registration date, etc.) - Paginate through large customer lists using limit and offset parameters - Sort customers by any field in ascending or descending order - Filter response to only include specific fields to reduce payload size Returns metadata with total customer count and an array of customer objects. |
| `HOTSPOTSYSTEM_CUSTOMERS_LIST_BY_LOCATION` | List Customers by Location | Lists all customers associated with a specific HotspotSystem location. Use this tool to: - Retrieve customer details (name, email, contact info, registration date) for a specific location - Paginate through large customer lists using limit and offset parameters - Sort customers by any field (prepend '-' for descending order, e.g., '-registered_at') - Filter response to include only specific fields to reduce payload size - Query customers at different locations by location ID Returns metadata with total customer count and an array of customer objects. Note: Empty results (total_count: 0) indicate no customers are registered at the specified location. |
| `HOTSPOTSYSTEM_GENERATE_VOUCHER_V1` | Generate Voucher (v1) | Generates an access voucher code on-demand for a specific location. This action creates a single-use voucher that can be used for hotspot access. The voucher is generated against available voucher credits in the specified location. Use this when you need to provide immediate access codes to users. Note: Requires an active location with available voucher credits (use the List Locations action first to get valid location_id values). |
| `HOTSPOTSYSTEM_GET_LOCATIONS_OPTIONS` | Get Locations Options | Tool to get simplified list of locations as dropdown options. Returns only id/name pairs for each location. Use when you need location options for selection menus or dropdowns. |
| `HOTSPOTSYSTEM_GET_ME` | Get Me | Tool to verify the resource owner's credentials and retrieve authenticated user information. Use when you need to confirm authentication status or get the current user's ID and operator name. |
| `HOTSPOTSYSTEM_LIST_PAID_TRANSACTIONS` | List Paid Transactions | Tool to list paid transactions globally across all locations. Use when you need to retrieve all paid transaction records with optional pagination and sorting. |
| `HOTSPOTSYSTEM_LOCATIONS_LIST` | List Locations | Tool to list the resource owner's locations. Use when you need to retrieve locations with optional filtering, sorting, or pagination. |
| `HOTSPOTSYSTEM_MISC_PING` | Misc Ping | Tool to perform health check against the HotspotSystem API. Use when verifying connectivity and availability. |
| `HOTSPOTSYSTEM_SUBSCRIBERS_LIST` | List Subscribers | List newsletter subscribers across all locations with optional filtering, sorting, and pagination. Returns subscriber information including contact details (name, email, phone, address) and social network data (Facebook, Google, etc.). Supports field selection to retrieve only needed properties, sorting by any field (ascending or descending), and pagination with limit/offset for large result sets. Use this tool when you need to: - Retrieve all subscribers for the account - Filter subscribers by specific fields - Sort subscribers by registration date, name, email, etc. - Paginate through large subscriber lists |
| `HOTSPOTSYSTEM_SUBSCRIBERS_LIST_BY_LOCATION` | List Subscribers by Location | Tool to list subscribers by location. Use when you need to retrieve subscribers for a specific location with optional field selection, sorting, and pagination. |
| `HOTSPOTSYSTEM_TRANSACTIONS_LIST_MAC` | List MAC Transactions | Tool to list MAC-based transactions. Use when you need to retrieve MAC transaction records with optional pagination and sorting. |
| `HOTSPOTSYSTEM_TRANSACTIONS_LIST_MAC_BY_LOCATION` | List MAC Transactions by Location | Lists MAC address authentication transactions for a specific location. MAC (Media Access Control) transactions track network access granted based on device MAC addresses. Use this action when you need to: - View MAC-based authentication history for a specific location - Monitor which devices accessed the network via MAC authentication - Retrieve transaction records with customer data and custom fields - Filter and paginate MAC transaction records for reporting For transactions across all locations, use the global MAC transactions endpoint instead. |
| `HOTSPOTSYSTEM_TRANSACTIONS_LIST_PAID_BY_LOCATION` | List Paid Transactions by Location | Tool to list paid transactions by location. Use when you need to retrieve paid transaction records for a specific location with optional pagination and sorting. |
| `HOTSPOTSYSTEM_TRANSACTIONS_LIST_SOCIAL` | List Social Transactions | Tool to list social transactions. Use when you need to retrieve social transaction records with optional pagination and sorting. |
| `HOTSPOTSYSTEM_TRANSACTIONS_LIST_SOCIAL_BY_LOCATION` | List Social Transactions by Location | Tool to list social transactions by location. Use when you need to retrieve social transaction records for a specific location with optional pagination and sorting. |
| `HOTSPOTSYSTEM_TRANSACTIONS_LIST_VOUCHER` | List Voucher Transactions | Tool to list voucher transactions globally across all locations. |
| `HOTSPOTSYSTEM_TRANSACTIONS_LIST_VOUCHER_BY_LOCATION` | List Voucher Transactions by Location | Tool to list voucher transactions by location. Use when you need to retrieve voucher transaction records for a specific location with optional pagination and sorting. |
| `HOTSPOTSYSTEM_VOUCHERS_LIST` | List Vouchers | Tool to list the resource owner's vouchers across all locations. Use when you need to retrieve vouchers with optional filtering, sorting, or pagination. |
| `HOTSPOTSYSTEM_VOUCHERS_LIST_BY_LOCATION` | Vouchers List by Location | Retrieves all vouchers associated with a specific location in the HotspotSystem. Use this action to: - List all vouchers available at a particular location - Filter voucher results by specific fields - Sort vouchers by any field (e.g., validity, price) - Implement pagination for large voucher lists Each voucher includes details such as serial number, access code, usage limits (traffic/download/upload), validity period, and pricing information. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Hotspotsystem MCP server is an implementation of the Model Context Protocol that connects your AI agent to Hotspotsystem. It provides structured and secure access so your agent can perform Hotspotsystem operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Python 3.9 or higher
- A Composio account and API key
- A Hotspotsystem connection authorized in Composio
- An OpenAI API key for the CrewAI LLM
- Basic familiarity with Python

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

**What's happening:**
- composio connects your agent to Hotspotsystem via MCP
- crewai provides Agent, Task, Crew, and LLM primitives
- crewai-tools[mcp] includes MCP helpers
- python-dotenv loads environment variables from .env
```bash
pip install composio crewai crewai-tools[mcp] python-dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates with Composio
- USER_ID scopes the session to your account
- OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

**What's happening:**
- CrewAI classes define agents and tasks, and run the workflow
- MCPServerHTTP connects the agent to an MCP endpoint
- Composio will give you a short lived Hotspotsystem MCP URL
```python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
```

### 5. Create a Composio Tool Router session for Hotspotsystem

**What's happening:**
- You create a Hotspotsystem only session through Composio
- Composio returns an MCP HTTP URL that exposes Hotspotsystem tools
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["hotspotsystem"])

url = session.mcp.url
```

### 6. Initialize the MCP Server

**What's Happening:**
- Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
- MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
- Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
- Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
- Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
```python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
```

### 7. Create a CLI Chatloop and define the Crew

**What's Happening:**
- Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
- Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
- Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
- Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
- Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
- Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.
```python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

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

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

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
```

## Complete Code

```python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["hotspotsystem"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

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

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

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")
```

## Conclusion

You now have a CrewAI agent connected to Hotspotsystem through Composio's Tool Router. The agent can perform Hotspotsystem operations through natural language commands.
Next steps:
- Add role-specific instructions to customize agent behavior
- Plug in more toolkits for multi-app workflows
- Chain tasks for complex multi-step operations

## How to build Hotspotsystem MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/hotspotsystem/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/hotspotsystem/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/hotspotsystem/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/hotspotsystem/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/hotspotsystem/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/hotspotsystem/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/hotspotsystem/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/hotspotsystem/framework/cli)
- [Google ADK](https://composio.dev/toolkits/hotspotsystem/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/hotspotsystem/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/hotspotsystem/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/hotspotsystem/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/hotspotsystem/framework/llama-index)

## Related Toolkits

- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Google Calendar](https://composio.dev/toolkits/googlecalendar) - Google Calendar is a time management service for scheduling meetings, events, and reminders. It streamlines personal and team organization with integrated notifications and sharing options.
- [Google Drive](https://composio.dev/toolkits/googledrive) - Google Drive is a cloud storage platform for uploading, sharing, and collaborating on files. It's perfect for keeping your documents accessible and organized across devices.
- [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.
- [Twitter](https://composio.dev/toolkits/twitter) - Twitter is a social media platform for sharing real-time updates, conversations, and news. Stay connected, informed, and engaged with communities worldwide.
- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Supabase](https://composio.dev/toolkits/supabase) - 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.
- [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Google Docs](https://composio.dev/toolkits/googledocs) - Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.
- [Google Super](https://composio.dev/toolkits/googlesuper) - Google Super is an all-in-one suite combining Gmail, Drive, Calendar, Sheets, Analytics, and more. It gives you a unified platform to manage your digital life, boosting productivity and organization.
- [Hubspot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - 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.
- [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Ashby](https://composio.dev/toolkits/ashby) - Ashby is an applicant tracking system that handles job postings, candidate management, and hiring analytics.
- [Pipedrive](https://composio.dev/toolkits/pipedrive) - Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Hotspotsystem MCP?

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.

### Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI 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.

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

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.

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)