Integration

HotspotSystem integration

HotspotSystem runs paid and free Wi-Fi hotspots (captive portal, vouchers, social and MAC login). Read your hotspot locations, the customers and newsletter subscribers they registered, the access vouchers you sell and the paid, voucher, social and MAC login transactions, for the whole account or one location. The API is read-only: creating vouchers, locations and webhooks is done in the HotspotSystem Control Center. Hotspot users' postal addresses, browser user agents, questionnaire answers, social profile links and details, and the device MAC addresses of MAC logins are not returned. Authentication is an API key, generated in Control Center > Tools & Settings > API Keys, sent in the sn-apikey header.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in HotspotSystem.Built from the 18 HotspotSystem tools below, on the connection you add once.

What you can do with HotspotSystem

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Voucher, 4 operations

  • list_location_vouchersList location vouchersGETLists the access vouchers of one location with their codes, time validity, traffic limits, simultaneous use and price. Paged with limit and offset; metadata.total_count gives the total.
  • list_location_voucher_transactionsList location voucher transactionsGETLists voucher login transactions of one location: date, amount, currency and the hotspot user's entered details. Paged with limit and offset; metadata.total_count gives the total.
  • list_vouchersList vouchersGETLists the account's access vouchers with their codes, time validity, traffic limits, simultaneous use and price. Paged with limit and offset; metadata.total_count gives the total.
  • list_voucher_transactionsList voucher transactionsGETLists voucher login transactions across all locations: date, location, amount, currency and the hotspot user's entered details. Paged with limit and offset; metadata.total_count gives the total.

Customer, 2 operations

  • list_customersList customersGETLists the customers (registered hotspot users) of every location of the account: name, user name, e-mail, phone, country, registration time. Paged with limit and offset; metadata.total_count gives the total.
  • list_location_customersList location customersGETLists the customers (registered hotspot users) of one location: name, user name, e-mail, phone, country, registration time. Paged with limit and offset; metadata.total_count gives the total.

Mac, 2 operations

  • list_location_mac_transactionsList location mac transactionsGETLists MAC-address login transactions of one location (date, access package, the user's entered details). The MAC address itself is not returned. Paged with limit and offset; metadata.total_count gives the total.
  • list_mac_transactionsList mac transactionsGETLists MAC-address login transactions across all locations (date, location, access package, the user's entered details). The MAC address itself is not returned. Paged with limit and offset; metadata.total_count gives the total.

Paid, 2 operations

  • list_location_paid_transactionsList location paid transactionsGETLists paid access transactions of one location: date, amount, currency and the hotspot user's entered details. Paged with limit and offset; metadata.total_count gives the total.
  • list_paid_transactionsList paid transactionsGETLists paid access transactions across all locations: date, location, amount, currency and the hotspot user's entered details. Paged with limit and offset; metadata.total_count gives the total.

Social, 2 operations

  • list_location_social_transactionsList location social transactionsGETLists social network login transactions of one location: date, access package and the hotspot user's entered details. Paged with limit and offset; metadata.total_count gives the total.
  • list_social_transactionsList social transactionsGETLists social network login transactions across all locations: date, location, access package and the hotspot user's entered details. Paged with limit and offset; metadata.total_count gives the total.

Subscriber, 2 operations

  • list_location_subscribersList location subscribersGETLists the newsletter subscribers of one location: name, user name, e-mail, phone, country, registration time. Paged with limit and offset; metadata.total_count gives the total.
  • list_subscribersList subscribersGETLists the newsletter subscribers of every location of the account: name, user name, e-mail, phone, country, registration time. Paged with limit and offset; metadata.total_count gives the total.

Location, 1 operation

  • list_locationsList locationsGETLists the account's hotspot locations (id and name). Use a location id with the list_location_* tools. Paged with limit and offset; metadata.total_count gives the total.

Me, 1 operation

  • get_meGet meGETVerifies the API key and returns the account it belongs to: the numeric userId and the operator name.

Option, 1 operation

  • list_location_optionsList location optionsGETLists the account's hotspot locations as id and name pairs, unpaged, for filling a location picker.

Ping, 1 operation

  • pingPingGETChecks that the HotspotSystem API is reachable; answers {"ping": "pong"}. Needs no data from the account.

Use HotspotSystem from Claude Code, Cursor or Codex

Connect HotspotSystem in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its HotspotSystem operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect HotspotSystem

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect HotspotSystem once

    Add your HotspotSystem connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

HotspotSystem integration FAQ

What can you do with the HotspotSystem integration?

LiveContext exposes 18 operations on HotspotSystem, covering voucher, customer, mac and paid.

Popular integrations

Browse the whole catalog