Skip to main content

MCP Server — Platform

The Aida Platform exposes a Model Context Protocol (MCP) endpoint so external AI clients can call the cloud assistant with the same multi-agent routing used in the Platform Assistant UI.

Endpoint​

EnvironmentURL
Productionhttps://api.aida-platform.com/api/assistant/mcp
Your deployment{platform-api-host}/api/assistant/mcp

Authenticate with a Platform API key:

X-API-Key: aida_your_api_key_here

Create keys in Platform Settings → API Keys — see API Keys — Platform.

:::info Platform vs controller MCP This MCP talks to the cloud assistant. Configure, commission, and operate a specific appliance through MCP Server — Controller. :::

What you can do​

Typical tools include assistant-oriented actions such as:

  • chat — natural-language conversation with session continuity
  • query — focused information requests
  • optimize / status-style tools — depending on the deployed tool catalog

List tools from your client:

curl -X POST https://api.aida-platform.com/api/assistant/mcp \
  -H "X-API-Key: aida_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{"method": "tools/list"}'

Call a tool (shape may follow tools/call or your client’s MCP transport):

curl -X POST https://api.aida-platform.com/api/assistant/mcp \
  -H "X-API-Key: aida_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "tools/call",
    "tool": "chat",
    "arguments": {
      "message": "What is my energy usage?",
      "sessionId": "my-session-123"
    }
  }'

Reuse the same sessionId to keep conversation context across turns.

Clients​

Any HTTP client or MCP-compatible app that can POST to this URL with X-API-Key can integrate. Prefer server-side callers; do not embed Platform API keys in browsers.

Rate limits follow your API key configuration.