MCP transport¶
Ewooks exposes one authenticated HTTP POST endpoint. Tool names are carried in JSON-RPC messages; they are not separate REST URLs.
Supported requests¶
| Method | Behavior |
|---|---|
initialize |
Returns the negotiated protocol version, server version and capabilities |
notifications/initialized |
Notification without an id; HTTP 202, empty body |
ping |
Returns an empty result object |
tools/list |
Lists the four tools and their JSON input schemas |
tools/call |
Runs a fleet-scoped read operation |
The server advertises protocol versions 2025-03-26, 2025-06-18 and 2025-11-25. Prefer 2025-11-25 and use the version returned by initialize. An unsupported explicit MCP-Protocol-Version header is rejected.
Message shape¶
{
"jsonrpc": "2.0",
"id": 42,
"method": "tools/call",
"params": {
"name": "list_drives",
"arguments": {
"from": "2026-11-20",
"to": "2026-11-20",
"pagination": "snapshot",
"limit": 100
}
}
}
Use an integer or string id and match the response to it. JSON-RPC batch arrays are not supported. Requests must be JSON objects and at most 65,536 raw bytes.
The current transport returns ordinary JSON responses. It does not require a long-lived GET stream, SSE subscription or Mcp-Session-Id. HTTP GET is rejected with 405.
Tool responses¶
Successful calls return the same data as structured JSON and text:
{
"jsonrpc": "2.0",
"id": 42,
"result": {
"content": [{"type": "text", "text": "{\"period\":{\"from\":\"2026-11-20\",\"to\":\"2026-11-20\"},\"drives\":[],\"pagination\":\"snapshot\",\"next_cursor\":null,\"snapshot_at\":\"2026-11-21T10:00:00Z\",\"expires_at\":\"2026-11-21T10:15:00Z\"}"}],
"structuredContent": {
"period": {"from": "2026-11-20", "to": "2026-11-20"},
"drives": [],
"pagination": "snapshot",
"next_cursor": null,
"snapshot_at": "2026-11-21T10:00:00Z",
"expires_at": "2026-11-21T10:15:00Z"
},
"isError": false
}
}
Prefer structuredContent. Do not concatenate or double-count the text representation as a second dataset. See errors for failed calls.
Backend clients and browsers¶
A backend client ordinarily omits the browser Origin header. Browser origins are restricted by the server. These docs do not provide a browser API-key console; keep credentials and fleet data in your backend.
For the underlying protocol, see the MCP specification.