Connect MCP - Aeolo

Aeolo exposes remote MCP at:

POST https://mcp.aeolo.io/mcp

Required headers

Authorization: Bearer atok_...
Content-Type: application/json
Accept: application/json, text/event-stream

The Accept header matters because the endpoint uses Streamable HTTP transport.

Initialize

curl -sS https://mcp.aeolo.io/mcp \
  -H "Authorization: Bearer $AEOLO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {},
      "clientInfo": { "name": "example-agent", "version": "0.1.0" }
    }
  }'

List tools

curl -sS https://mcp.aeolo.io/mcp \
  -H "Authorization: Bearer $AEOLO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/list",
    "params": {}
  }'

The default endpoint exposes task-specific tools such as aeo_get_brand_context, aeo_get_content and aeo_import_article, alongside view tools. The command gateways aeo_read and aeo_execute_command are available at https://mcp.aeolo.io/mcp?surface=full.

Run an Aeolo command

domainId takes a domain ID, host or brand name, and can be omitted when the account has one domain.

curl -sS "https://mcp.aeolo.io/mcp?surface=full" \
  -H "Authorization: Bearer $AEOLO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 3,
    "method": "tools/call",
    "params": {
      "name": "aeo_read",
      "arguments": {
        "command": "agent context",
        "domainId": "brand.com"
      }
    }
  }'

See MCP Tools for schemas and Command Execution for routing behavior.