How to integrate Hotspotsystem MCP with Codex

Framework Integration Gradient
Hotspotsystem Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Hotspotsystem MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Hotspotsystem MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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 & Triggers

Tools
List CustomersTool to list customers.
List Customers by LocationTool to list customers by location.
Generate Voucher (v1)Tool to generate an access voucher on the fly.
List LocationsTool to list the resource owner's locations.
Misc PingTool to perform health check against the HotspotSystem API.
List SubscribersTool to list newsletter subscribers.
List Subscribers by LocationTool to list subscribers by location.
List MAC TransactionsTool to list MAC-based transactions.
List MAC Transactions by LocationTool to list MAC transactions by location.
List Paid Transactions by LocationTool to list paid transactions by location.
List Social TransactionsTool to list social transactions.
List Social Transactions by LocationTool to list social transactions by location.
List Voucher TransactionsTool to list voucher transactions globally across all locations.
List Voucher Transactions by LocationTool to list voucher transactions by location.
List VouchersTool to list the resource owner's vouchers across all locations.
Vouchers List by LocationTool to list vouchers by location.

Conclusion

You've successfully integrated Hotspotsystem with Codex using Composio's Rube MCP server. Now you can interact with Hotspotsystem directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Hotspotsystem operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Hotspotsystem operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Hotspotsystem MCP Agent with another framework

FAQ

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 Codex?

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

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