FolioX MCP¶
Back-office fuel dispatch for AI agents. The FolioX MCP server lets an AI assistant — Claude, a custom agent, or your own automation — work your dispatch board over the FolioX platform: draft, validate, and publish load assignments, check live tank inventory and runout forecasts, review a load's full audit timeline, and manage existing loads. All of it runs under your FolioX account, with your existing roles, permissions, and tenant scoping.
- **Endpoint** — `https://mcp.foliox.ai/mcp` (MCP Streamable HTTP)
- **Agent digest** — [`/llms.txt`](https://mcp.foliox.ai/llms.txt)
What agents can do¶
| Capability | Tools |
|---|---|
| Plan a load end to end | get_build_context → validate_load → create_load |
| Answer dispatch questions | find_loads, get_load, get_load_timeline |
| Watch inventory | query_inventory, get_recommended_loads |
| Manage existing loads | update_load_status, reassign_load, update_load |
| Tell us what's missing | report_missing_capability |
The golden path — from "send 5,000 gallons of regular to Canco 131 Clement tomorrow morning" to a published, driver-assigned load — takes an agent four tool calls, with a dry-run validation and a human confirmation before anything is written.
Design principles¶
- Names in, ids out. Agents pass site, driver, and product names; every response carries the id next to the name. Agents echo ids back — they never construct one.
- The backend is the boundary. The MCP server holds no authorization logic of its own. Your credential is forwarded on every call and the FolioX backend enforces tenant scoping, roles, and scopes exactly as it does for the FolioX app.
- Writes are double-gated. Nothing is created or changed without a server-issued token bound to the exact payload and a human confirmation. See Write Safety.
- Honest results. List tools report
totalvsshown; unknown sites return an explicit "no match" hint rather than a guess; partial failures are flagged loudly.
Start here¶
- Quickstart — connect from claude.ai, Claude Code, or your own agent in under two minutes.
- Authentication — interactive OAuth vs. API keys.
- Tools Reference — every tool, parameter by parameter.