# How to integrate Hotspotsystem MCP with OpenAI Agents SDK

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

## Introduction

This guide walks you through connecting Hotspotsystem to the OpenAI Agents SDK 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 OpenAI Agents SDK 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 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)
- [CrewAI](https://composio.dev/toolkits/hotspotsystem/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Install the necessary dependencies
- Initialize Composio and create a Tool Router session for Hotspotsystem
- Configure an AI agent that can use Hotspotsystem as a tool
- Run a live chat session where you can ask the agent to perform Hotspotsystem operations

## What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.
Key features include:
- Hosted MCP Tools: Connect to external services through hosted MCP endpoints
- SQLite Sessions: Persist conversation history across interactions
- Simple API: Clean interface with Agent, Runner, and tool configuration
- Streaming Support: Real-time response streaming for interactive applications

## 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:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Hotspotsystem project
- Some knowledge of Python or Typescript

### 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).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

What's happening:
- You're importing all necessary libraries.
- The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Hotspotsystem.
```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
```

```typescript
dotenv.config();

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

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only hotspotsystem.
- The router checks the user's Hotspotsystem connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Hotspotsystem.
- This approach keeps things lightweight and lets the agent request Hotspotsystem tools only when needed during the conversation.
```python
# Create a Hotspotsystem Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["hotspotsystem"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Hotspotsystem
const session = await composio.create(userId as string, {
  toolkits: ['hotspotsystem'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Hotspotsystem. "
        "Help users perform Hotspotsystem operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Hotspotsystem. Help users perform Hotspotsystem operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

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

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

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

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

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

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

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

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["hotspotsystem"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Hotspotsystem. "
        "Help users perform Hotspotsystem operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

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

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['hotspotsystem'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Hotspotsystem. Help users perform Hotspotsystem operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

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

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

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

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

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

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\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

This was a starter code for integrating Hotspotsystem MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Hotspotsystem.
Key features:
- Hosted MCP tool integration through Composio's Tool Router
- SQLite session persistence for conversation history
- Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## How to build Hotspotsystem MCP Agent with another framework

- [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)
- [CrewAI](https://composio.dev/toolkits/hotspotsystem/framework/crew-ai)

## 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 OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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)