Connect an assistant
Drive fOS from an external AI assistant — Claude, ChatGPT, or any MCP client — by pointing it at the fOS Agent API at mcp.tovr.eu and authenticating with an API key or the OAuth browser flow.
You can drive fOS from an external assistant — Claude, ChatGPT, or any client that speaks the Model Context Protocol — so it can search loads, read economics, and act on your behalf from inside that assistant. This guide is the quick path; the full spec is the Agent API reference.
What you need
- An fOS API key (
tovr_…), or an MCP client that supports the OAuth browser flow. - The MCP endpoint:
https://mcp.tovr.eu/mcp.
Connect an MCP client
- Add a custom MCP server in your assistant, pointing at
https://mcp.tovr.eu/mcp. - Authenticate:
- API key — provide your
tovr_…key as a bearer token, or - OAuth — clients that support it auto-discover the OAuth configuration and open a browser consent flow (OAuth 2.1 with PKCE).
- API key — provide your
- If you belong to more than one organization, fOS will establish which one is in context via
list_my_orgs/switch_orgbefore acting.
Once connected, the assistant can call the tools flagged MCP ✓ in the tool reference — chiefly the decision-grade reads plus a controlled set of actions.
What the assistant can and can't do
Exposure is deliberately scoped on this surface: reads are broadly available, writes are gated, and some sensitive actions (like connecting an integration) never leave the TOVR web app. See Guardrails › scoped exposure.
Non-MCP clients
If your client doesn't speak MCP, use the REST bridge:
GET /api/v1/tools to list tools and POST /api/v1/tools/{toolName} to invoke one, with the same
authentication and scopes.
Negotiate within the floor
The fOS run for a live rate call — read the shipper before you talk, check each counter-offer against the margin floor without ever revealing it, report the outcome, and escalate to a human when the deal needs authority beyond fOS. Runs on the voice surface.
Tool arsenal
The categories of tools fOS can invoke, mapped to the mission loop — fleet, load search & bidding, chain economics, market intelligence, outreach, live negotiation, workspace (email/calendar/drive), and session/context. A per-tool reference generated from the contract registry follows.