Connecting an AI assistant (MCP)

Consibio Cloud has an MCP (Model Context Protocol) server that lets AI assistants — like Claude — work with your projects directly: reading live and historical measurements, checking device status, and managing alarms, all with your own account’s permissions.

What you need

• A Consibio Cloud account.
• A Consibio API token (a Bearer token). See Consibio Cloud API for how to get one.
• An MCP-capable assistant, e.g. Claude (Desktop app or claude.ai).

Connect Claude Desktop

1. Open your Claude Desktop configuration file:

   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add the Consibio Cloud MCP server, replacing YOUR_TOKEN with your API token:

   {
     "mcpServers": {
       "consibio-cloud": {
         "type": "http",
         "url": "https://mcp.consibio.cloud/mcp",
         "headers": {
           "Authorization": "Bearer YOUR_TOKEN"
         }
       }
     }
   }

3. Restart Claude Desktop. The Consibio Cloud tools appear in the tools menu.

Other MCP clients work the same way: point them at https://mcp.consibio.cloud/mcp (streamable HTTP transport) with an Authorization: Bearer YOUR_TOKEN header.

What the assistant can do

The MCP server exposes the Consibio Cloud API as tools, so the assistant can — within your account’s permissions — for example:

• list your projects, devices and elements,
• read live values and historical datalog,
• check device health and uptime,
• create and manage alarms, reports and widgets.

Try prompts like “What’s the current temperature in my greenhouse project?” or “Which of my devices have been offline in the last 24 hours?”.

Security notes

• The assistant acts as you: it can only see projects you’re a member of, and its writes are limited by your role.
• Treat your API token like a password. Don’t share configs containing it, and revoke it if it leaks.

Troubleshooting

• The tools don’t appear — check the config file is valid JSON and restart the client.
• Authentication errors — your token may have expired; generate a new one (see Consibio Cloud API).

Still stuck? Contact support@consibio.com.