Ask Claude which devices are offline, what a sensor last read, or how a variable trended over the past week — without opening a dashboard.
Let an AI agent create devices, update device types, or reorganize device groups as you describe the change in plain language.
Open, acknowledge, comment on, or assign incidents through natural-language prompts — no need to touch the Ubidots UI.
Grab your token from your Ubidots profile. It's what authenticates your AI client — no separate account or sign-up needed.
Paste the endpoint (https://mcp.ubidots.com/mcp) and your token into your AI client's config. See Configuration below for exact steps per client.
Ask about your devices, variables, or incidents in plain language. Your AI calls Ubidots directly and answers — no dashboard required.
Example prompts
Once it's connected, just ask in plain language. Your AI decides which Ubidots tools to call and answers with your real data.
Reading data
“Which devices are offline?”
“Show the last temperature values for device aws810.”
“What was the average temperature of Machine ABC yesterday?”
“List organizations and show the device count for each.”
Creating and updating data
“Create a new device called pump-04 under the Plant North organization.”
“Update the description of device aws810 to ‘North wing compressor’.”
“Create a P2 incident for device aws810 about a sensor fault.”
{
"mcpServers": {
"ubidots": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.ubidots.com/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer <YOUR UBIDOTS TOKEN>"
}
}
}
}Edit claude_desktop_config.json, paste this in, swap in your token, restart Claude Desktop.
curl https://api.anthropic.com/v1/messages \
-H "x-api-key: $ANTHROPIC_API_KEY" \
-H "anthropic-version: 2023-06-01" \
-H "anthropic-beta: mcp-client-2025-11-20" \
-H "content-type: application/json" \
-d '{
"model": "claude-opus-5-5",
"max_tokens": 1024,
"messages": [
{"role": "user", "content": "Which of my devices are offline?"}
],
"mcp_servers": [{
"type": "url",
"name": "ubidots",
"url": "https://mcp.ubidots.com/mcp",
"authorization_token": "YOUR_UBIDOTS_TOKEN"
}],
"tools": [
{"type": "mcp_toolset", "mcp_server_name": "ubidots"}
]
}'Call this from your own app (a Slack or WhatsApp bot, or a chat inside your Ubidots application) to give Claude your Ubidots tools. Swap in your Anthropic API key and your Ubidots token.
Any MCP-compatible client can connect directly to https://mcp.ubidots.com/mcp using your API token as a bearer token in the Authorization header.
Each category can be scoped to read-only or isolated to just that entity — see Authentication below.
Read
Only fetches data
Write
Creates or changes records (off on /readonly endpoints)
Devices
List devices
Read
Latest values
Read
Create
Write
Update
Write
Variables
List variables
Read
List by device
Read
Statistics
Read
Time series
Read
Create
Write
Update
Write
Statistics: first, last, min, max, count, sum, mean, standard deviation, and the 25th, 50th and 75th percentiles.
Device groups
List
Read
Create
Write
Update
Write
Device types
List
Read
Create
Write
Update
Write
Organizations
List
Read
Create
Write
Update
Write
Events
List events
Read
Event logs
Read
No write tools for events yet.
Incidents
List incidents
Read
Incident logs
Read
Create
Write
Acknowledge
Write
Comment
Write
Assign
Write
Ubidots MCP Server authenticates with your existing Ubidots API token — no separate account, no OAuth flow to set up.
Pass it as a bearer token in the Authorization header (Authorization: Bearer <your token>) — the same token you already use for the Ubidots REST API.
Need narrower access? Point your AI client at a scoped endpoint — see the table below — to restrict it to read-only, or to a single entity type — useful for giving an assistant the minimum access it needs.
Full access (read and write)
https://mcp.ubidots.com/mcp
Full access, read-only
https://mcp.ubidots.com/mcp/readonly
Devices only
https://mcp.ubidots.com/mcp/_/devices
Devices, read-only
https://mcp.ubidots.com/mcp/_/devices/readonly
Variables only
https://mcp.ubidots.com/mcp/_/variables
Variables, read-only
https://mcp.ubidots.com/mcp/_/variables/readonly
Device groups only
https://mcp.ubidots.com/mcp/_/device-groups
Device groups, read-only
https://mcp.ubidots.com/mcp/_/device-groups/readonly
Device types only
https://mcp.ubidots.com/mcp/_/device-types
Device types, read-only
https://mcp.ubidots.com/mcp/_/device-types/readonly
Organizations only
https://mcp.ubidots.com/mcp/_/organizations
Organizations, read-only
https://mcp.ubidots.com/mcp/_/organizations/readonly
Events only (no write tools yet)
https://mcp.ubidots.com/mcp/_/events
Events, read-only
https://mcp.ubidots.com/mcp/_/events/readonly
Incidents only
https://mcp.ubidots.com/mcp/_/incidents
Incidents, read-only
https://mcp.ubidots.com/mcp/_/incidents/readonly
Check that your API token is valid and correctly formatted as Bearer <token> in the Authorization header — a missing "Bearer" prefix or an expired token are the most common causes.
Confirm your network allows outbound HTTPS to mcp.ubidots.com, and that the endpoint is typed exactly as https://mcp.ubidots.com/mcp.
Check you're using the full endpoint, not a scoped read-only or entity-specific one — scoped endpoints intentionally expose fewer tools.
Remove any duplicate server entries in your AI client's MCP config file — each server should be listed once.
Claude Desktop (macOS, Windows, Linux) and the Anthropic API today; any MCP-compatible client can also connect directly using the same endpoint and token.
Yes — use a scoped endpoint (read-only, or limited to one entity type) instead of the full https://mcp.ubidots.com/mcp.
Get started
Point Claude or any MCP-compatible client at the Ubidots MCP Server and authenticate with your existing Ubidots API token. It's hosted by Ubidots, so there's nothing to install.