Ewooks MCP API · Developer guide
Fleet data. In your workflow.¶
Read mileage-log drives and work diary entries from your own fleet. Connect an ordinary server-side program using HTTPS and JSON-RPC — no chat session or language model is required.
Connection details¶
| Environment | MCP endpoint |
|---|---|
| Production | https://my.ewooks.fi/api/mcp |
| Demo | https://demot.cabimap.com/api/mcp |
These are service locations, not a promise that release 0.2 is installed. See release status, then check the version returned by initialize before using snapshot pagination.
The transport is MCP over HTTP POST, using JSON-RPC 2.0. This release does not provide REST routes such as /v1/drives, write operations, webhooks, or a change feed.
What you can read¶
| Tool | Purpose |
|---|---|
list_drives |
Individual work-classified drives, their distances and optional job references |
summarize_drives |
Drive counts and recorded distance, total and by driver |
list_work_sessions |
Individual work diary sessions and recorded hours |
summarize_work_sessions |
Work-session counts and recorded hours, total and by driver |
Every request is authorized for one fleet from the credential. A request cannot select another company or fleet. In release 0.2, drive tools exclude both private and unclassified drives.
Plan your integration¶
- Arrange access with the fleet owner and Ewooks. Access is not enabled automatically for every account.
- Create a named key for your integration and store it on your backend.
- Use a bounded date range and snapshot pagination to obtain the data.
- Map the returned identifiers to your own employee, vehicle and job identifiers.
- Apply your own review, approval, duplicate prevention and downstream business rules.
Recorded distance is not automatically reimbursable or billable distance. A saved job reference is not a verified target-system work order. Read data lifecycle before using the data for payroll or invoicing.