Integration

ClearBlade integration

ClearBlade IoT Enterprise is an IoT application platform (cloud, on-premises or edge). Read, insert, update and delete rows of a system's data collections with SQL-like queries, run code services, publish MQTT messages and count topics, register, update, query and delete devices and see which are connected, list users and their connections, and read the timers and triggers that run code services. System administration (collections, code, roles, adapters, deployments, edges, portals, plugins, external databases, secrets, filestores, webhooks, Google integrations), message history, login, registration and two-factor routes are not exposed, and timer and trigger secrets are not returned. Authentication: the instance URL (for example https://platform.clearblade.com), the system key, and a user token sent in the ClearBlade-UserToken header; create a service account user in the console so its token does not expire.

Connect ClearBlade How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with ClearBlade

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.

Device, 5 operations

create_deviceCreate devicePOSTRegisters a new device in the system under the given name and returns it.
delete_devicesDelete devicesDELETEDeletes every device matching a query.
list_devicesList devicesGETLists the devices the token may see, with their name, type, state, description, enabled flag, authentication options and creation and last activity dates; filter with a query.
update_deviceUpdate devicePUTUpdates the state or custom attributes of one device and returns it.
update_devicesUpdate devicesPUTUpdates every device matching a query, setting the given column values, and returns the affected devices.

Collection, 4 operations

create_collection_itemsCreate collection itemsPOSTInserts one row, or several when given a list, into a collection and returns the item_id of each new row.
delete_collection_itemsDelete collection itemsDELETEDeletes every row of a collection matching a query and returns the number of rows deleted.
query_collection_itemsQuery collection itemsGETReads the rows of a collection, optionally filtered, sorted and paged with a query; returns the matching rows (DATA), their TOTAL count and the current page.
update_collection_itemsUpdate collection itemsPUTUpdates every row of a collection matching a query, setting the given column values, and returns the number of rows changed.

Connection, 3 operations

get_device_connectionGet device connectionGETReturns one device with its current MQTT connections (client_id and connection time).
list_connected_devicesList connected devicesGETLists the devices currently connected over MQTT, each with its connections (client_id and connection time).
list_connected_usersList connected usersGETLists the users currently connected over MQTT, as an object of user email to that user's connections.

Count, 3 operations

count_collection_itemsCount collection itemsGETCounts the rows of a collection, optionally only those matching a query.
count_devicesCount devicesGETReturns the total number of devices of the system.
count_topicsCount topicsGETReturns the number of topics of the system.

Code, 2 operations

execute_code_serviceExecute code servicePOSTRuns a code service of the system (server-side JavaScript) with the given parameters and returns what the service responds.
list_code_servicesList code servicesGETLists the names of the code services of the system.

Connectioncount, 2 operations

count_connected_devicesCount connected devicesGETReturns how many devices exist, how many are connected and the total number of device connections.
count_connected_usersCount connected usersGETReturns how many users exist, how many are connected and the total number of user connections.

Timer, 2 operations

get_timerGet timerGETReturns one timer: its code service, start time, frequency in seconds and number of repeats (-1 for forever).
list_timersList timersGETLists the timers of the system: which code service each runs, from when, how often (seconds) and how many times.

Trigger, 2 operations

get_triggerGet triggerGETReturns one trigger: the event definition and key-value conditions that start it, and the code service it runs.
list_triggersList triggersGETLists the triggers of the system: which event (for example a message on a topic) runs which code service.

Allcollection, 1 operation

list_collectionsList collectionsGETLists the collections (data tables) of the system the token belongs to, with each collection's name and collectionID.

Column, 1 operation

get_collection_columnsGet collection columnsGETLists the columns of a collection with their name, type and whether each is the primary key.

Info, 1 operation

get_current_userGet current userGETReturns the user the token belongs to: email, user_id and creation date.

Publish, 1 operation

publish_messagePublish messagePOSTPublishes a message on an MQTT topic of the system (with QoS 0, 1 or 2), provided the token's role may publish on that topic.

User, 1 operation

list_usersList usersGETLists the users of the system the token may see (email, user_id, creation date), optionally filtered with a query.

Use ClearBlade from Claude Code, Cursor or Codex

Connect ClearBlade in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its ClearBlade 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 ClearBlade

Create your workspace
Sign up free. Nothing to install.
Connect ClearBlade once
Add your ClearBlade connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.