MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external data sources.
With the Ubidots MCP Server, Claude or Cursor can call Ubidots tools as if they were power users.
Ask your AI which devices are offline, to pull a variable's time-series data, or to open an incident — it queries Ubidots directly and answers you, no dashboard required.
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.
{
"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.
"authorization_token": "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. (The source article gives no client-specific steps beyond the two above — needs product/support input before publishing a full tab set.)
Each category can be scoped to read-only or isolated to just that entity — see Authentication below.
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.
Read-only, full API
https://mcp.ubidots.com/mcp/readonly
Devices only
https://mcp.ubidots.com/mcp/_/devices
Devices, read-only
https://mcp.ubidots.com/mcp/_/devices/readonly
(Same pattern for variables, device groups, device types, organizations, events, incidents)
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.
