Create an Agent Connection
Open Agent Access in Fliox. Name the connection for the client and purpose, choose the smallest useful scopes, restrict company access, and set an expiration.
Fliox turns client operations into explicit tools an agent can discover, understand, and use safely. It can search, analyze, draft, update, and coordinate — while scopes, approvals, tenancy, and audit stay under human control.
fliox / agent-session
LIVE# orient before acting
› connection.whoami
› workspace.search "renewal cases at risk"
› projects.bulk_update_status.preview
› waiting for approval
01 / QUICKSTART
Each step narrows uncertainty before it increases authority.
Open Agent Access in Fliox. Name the connection for the client and purpose, choose the smallest useful scopes, restrict company access, and set an expiration.
Use the Streamable HTTP endpoint with the one-time Fliox bearer token. Claude, Codex, Cursor, and custom MCP clients can use the same server.
Start with connection.whoami, then resources/list. The agent learns its scopes, allowed companies, operating guide, safety rules, and current capability catalog.
Use workspace.search to find typed results, then load the exact project, task, document context, template, or page before planning an action.
Bulk updates and deletion begin with a preview. Fliox freezes the target ids and diff in a proposal and gives the agent an approval link for the human.
After approval, the agent executes the current proposal version, re-reads affected objects, and reports the result. Reversible operations expose a compensating rollback.
CLIENT CONFIGURATION
Use the same connection in any MCP-compatible client. Restrict it to the companies and scopes needed for that agent's job.
{
"mcpServers": {
"fliox": {
"url": "https://fliox.io/v1/mcp",
"headers": {
"Authorization": "Bearer fliox_mcp_••••••"
}
}
}
}02 / CAPABILITY MAP
Deterministic tools use the external agent's intelligence and Fliox's operational guardrails.
Orient the agent inside the exact personal or company workspace before it acts.
connection.whoamicompanies.listworkspace.searchworkspace.overviewcompany.overviewRead projects, tasks, readiness signals, and management metrics with links back to Fliox.
projects.listprojects.gettasks.listdocuments.contextcompany.analyticsCreate and update bounded objects with retry-safe, auditable writes.
clients.createprojects.create_from_templateprojects.update_detailsprojects.steps.createprojects.steps.moveprojects.reminders.createDraft, validate, translate, publish, and connect reusable templates and pages.
templates.validate_drafttemplates.create_drafttemplates.translation_upsertpages.createtemplate_pages.replaceWork with requirements and review metadata without placing private file bodies in MCP context.
projects.documents.list_requirementsdocuments.requirements.createdocuments.files.create_uploaddocuments.files.reviewsmart_forms.generate_pdfFreeze an exact target set and diff, ask a human, then execute or compensate.
projects.bulk_update_status.previewprojects.bulk_assign_responsible.previewtasks.bulk_update_status.previewchanges.executechanges.rollbackCall resources/list, then read fliox://capabilities/catalog. The response contains every tool schema, required scope, side-effect flag, approval policy, and the recommended operating sequence.
03 / HUMAN CHECKPOINT
Bulk and destructive operations never jump directly from intent to mutation. The preview stores the exact targets, current versions, visible diff, and rollback plan in Fliox.
Build exact targets and a human-readable diff.
*.previewOpen the deep link and release the proposal.
Agent AccessApply the approved version after all checks pass.
changes.executeRe-read state; roll back only when supported.
changes.rollback04 / WORKED EXAMPLES
Typed search returns match reasons and deep links without crossing the connection's workspace boundary.
{
"jsonrpc": "2.0",
"id": 12,
"method": "tools/call",
"params": {
"name": "workspace.search",
"arguments": {
"company_id": "018f…",
"query": "renewal",
"types": ["project", "task", "document_requirement"],
"limit": 25
}
}
}Project, task, document, and workload metrics include their definitions and calculation timestamp.
{
"jsonrpc": "2.0",
"id": 13,
"method": "tools/call",
"params": {
"name": "company.analytics",
"arguments": {
"company_id": "018f…"
}
}
}A stable retry key and exact project IDs produce a proposal. They do not update the projects yet.
{
"jsonrpc": "2.0",
"id": 14,
"method": "tools/call",
"params": {
"name": "projects.bulk_update_status.preview",
"arguments": {
"idempotency_key": "renewals-2026-07-16-v1",
"company_id": "018f…",
"project_ids": ["0190…", "0191…", "0192…"],
"status": "in_progress"
}
}
}05 / SAFETY MODEL
Every company operation requires an allowed company and an active owner or assistant role. Cross-tenant IDs resolve as not found.
Read and write scopes are issued per capability family. A token can be company-limited, expiring, and revoked instantly.
Every mutation carries a stable key. Identical retries replay safely; a changed payload with the same key is rejected.
Bulk and destructive changes stay frozen until a person approves the exact target set and diff inside Fliox.
documents.context returns readiness metadata and risks — never file bodies, storage keys, or private download URLs.
Tool, connection, role, object references, outcome, duration, and safe summaries remain visible in Agent Access.