Session & context
fOS plumbing tools — org scoping for external assistants (list/switch companies), asking the user for a missing detail, exporting data, connecting an integration, and the carrier auth tools for non-web surfaces.
Plumbing tools a surface needs to function — identity, org scoping, and connecting things. They don't move a deal themselves but make the loop runnable. See the arsenal overview for how to read the table.
Org context (MCP)
| Tool | Type | MCP | Purpose |
|---|---|---|---|
list_my_orgs | Read | ✓ | List the organizations the caller can act for. |
switch_org | Action | ✓ | Set the active organization for subsequent calls. |
On external assistants, where a user may belong to several orgs, these establish which org is in context before fOS operates — enforcing org-scoped access.
Interaction plumbing (web)
| Tool | Type | MCP | Purpose |
|---|---|---|---|
ask_user_for_details | Read | ✗ | Render a form to collect a missing detail (qualification). |
export_data | Read | ✗ | Export data from a result (web-only). |
connect_integration | Action | ✗ | Open the inline modal / deep-link to connect an integration. |
connect_integration never leaves the web surface — connecting a provider (OAuth, credentials)
is a first-party flow, not something an external assistant performs. When a tool needs an
integration that isn't connected, fOS surfaces this rather than failing silently.
Carrier auth (non-web surfaces)
| Tool | Type | MCP | Purpose |
|---|---|---|---|
request_otp | Action | ✗ | Request a one-time code to authenticate. |
authenticate_carrier | Action | ✗ | Authenticate a carrier with a code. |
register_carrier | Action | ✗ | Register a new carrier. |
logout_carrier | Action | ✗ | End the session. |
These support authentication on non-web surfaces (voice / onboarding). On the web, the user is already signed in through the dashboard, and on MCP the caller authenticates with the Agent API credentials.
Workspace
fOS tools that act in the user's Google/Microsoft workspace — compose helpers that draft mail, schedule events, and save files, plus the connected Gmail, Calendar, and Drive actions they hand off to. Requires a connected integration.
fOS Agent API
The developer interface to fOS at mcp.tovr.eu — connect an external assistant over the Model Context Protocol or the REST bridge, authenticate with an API key or OAuth 2.1 (DCR + PKCE), scope access read/write, and call fOS tools.