Skip to main content

Integrations

Floxar has an MCP server, so you can work in your account from your own AI client, or let software work in it under an identity of its own. Connect a client when you want to work in Floxar yourself: you sign in with your usual Floxar login, and each verified client has a short guide with the exact steps. Register an agent when software should act on its own, with its own role and its own place in the audit trail. Agents that act on your own systems can keep the credentials they need in the Secrets Vault, which Floxar can never read.

Connecting an AI client to Floxar​

Floxar has a Model Context Protocol (MCP) server, so you can work in Floxar from your own AI client: find and read your flows, steps, references and trails, run trails, and create or edit flows. You sign in with your usual Floxar login, and the client can only do what you approve and what your role in the account allows.

Registering an agent​

An agent is a non-human member of a Floxar account: an AI worker, an integration or a scheduled job that reads and runs your processes through Floxar's MCP tools, with its own credentials and its own role. It runs on your infrastructure and your own AI keys; Floxar gives it an identity, a permission level and a place in the audit trail. This article is for you if you are building or deploying one.

Using the Secrets Vault from an agent​

This article is for you if you build or run an agent that needs credentials from the Secrets Vault while it executes a flow. For what the Vault is, why Floxar cannot read what it stores, and how an admin sets it up, read The Secrets Vault first.

Agents and AI clients: which one you need​

There are two ways to reach Floxar's MCP tools: a person connects an AI client they use, or an account admin registers an agent that acts on its own. Both reach the same account URL, https://mcp.floxar.com/a/<account_id>, and the same tools, and both are limited by a role. The rest differs.

Creating trails in bulk with the API​

The batch endpoint creates many trails in one request: the same thing the Workload Generator does with a spreadsheet, for an integration that feeds work into Floxar on its own, such as a ticketing tool, a scheduler or an HR platform. Each row becomes a trail on the flow it names, already on that flow's first step, assigned to someone or waiting in the queue. The rows, their checks and the result are the same as an uploaded file's, so Creating trails in bulk with the Workload Generator is the reference for what each column means.

Connect Claude (claude.ai and Claude Desktop) to Floxar​

claude.ai and Claude Desktop share the same connectors, so you add Floxar once as a custom connector and use it in both. Claude identifies itself to Floxar with its own Client ID Metadata Document: you enter no client ID or secret. Reading, running trails and authoring through Claude are confirmed.

Connect Claude Code to Floxar​

You add Floxar to Claude Code with one command in your terminal. Claude Code identifies itself to Floxar with its own Client ID Metadata Document, so you enter no client ID or secret.

Connect VS Code to Floxar​

You use Floxar in VS Code from GitHub Copilot Chat in agent mode. VS Code identifies itself to Floxar with its own Client ID Metadata Document, so you enter no client ID or secret. The connection is confirmed with VS Code 1.139, the desktop editor.

Connect ChatGPT to Floxar​

ChatGPT connects to Floxar in developer mode, which is available on ChatGPT Pro, Plus, Business, Enterprise and Education accounts on the web; a workspace's policy can restrict it. ChatGPT identifies itself to Floxar with its own Client ID Metadata Document, so you enter no client ID or secret. Reading and running trails through ChatGPT are confirmed.

Connect Codex to Floxar​

The Codex command line, the Codex IDE extension and the ChatGPT desktop app share one configuration, so you add Floxar once. Codex identifies itself to Floxar with its own Client ID Metadata Document, so you enter no client ID or secret.

Connect Grok (grok.com) to Floxar​

You add Floxar to Grok on grok.com as a custom connector. Grok identifies itself with its own Client ID Metadata Document, so it needs no client ID or secret from you. Reading and running trails through Grok are confirmed. Grok Build, the command-line client, is a separate client with a guide of its own: Connect Grok Build.

Connect Cursor to Floxar​

Cursor's desktop application and command line share one mcp.json. Cursor publishes no metadata document, so it identifies itself with the identifier Floxar publishes for it, cursor. There is no client secret. The connection is confirmed with Cursor 3.22.12 (desktop).

Connect Grok Build to Floxar​

Grok Build, the command-line client, identifies itself with the identifier Floxar publishes for it, grok-build. There is no client secret. The connection is confirmed with Grok Build 1.0.44. Grok on grok.com is a separate client with a guide of its own: Connect Grok (grok.com).

Publishing a client metadata document​

If you build an MCP client, no registration with Floxar is needed. Publish a Client ID Metadata Document and use its HTTPS URL as your client_id. Floxar fetches the document when your client first asks to connect, and the URL's domain is what people see when they are asked to allow the connection. The rules are those of the IETF client-ID-metadata-document draft, with a few narrowings described here.

MCP tool reference: reading content​

Tools that read your account's content and runs: identity and platform description, flows, bits, references, trails and the current step. They need the floxar.read capability. This page is generated from the tools as Floxar's MCP server registers them, so names, inputs and descriptions match what your client receives. See also running trails and authoring content and administration.

MCP tool reference: running trails​

Tools that run flows as trails: start a trail, answer a step, move on, change its status, transfer it and add context. They need the floxar.execute capability. This page is generated from the tools as Floxar's MCP server registers them, so names, inputs and descriptions match what your client receives. See also reading content and authoring content and administration.

MCP tool reference: authoring content​

Tools that write content: create and update bits, flows, connections and references. They need the floxar.author capability. The props and markdown of each interactive element are in the element reference. This page is generated from the tools as Floxar's MCP server registers them, so names, inputs and descriptions match what your client receives. See also reading content and running trails and administration.

MCP element reference: interactive elements in a bit​

Every interactive element you can put in a bit over MCP: what it is for, the props it accepts, and a worked example. This page is generated from the rules Floxar's server applies, and every example on it was built by the server's own write path, so what you see is what a write accepts. The tools themselves are in authoring content.

MCP tool reference: administration​

Tools that administer an account: the administration feeds, settings, users and scopes, reached as operations through the admin dispatchers (describe_operations lists them). They need the floxar.admin capability, which only an Admin's grant carries. This page is generated from the tools as Floxar's MCP server registers them, so names, inputs and descriptions match what your client receives. See also reading content and running trails and authoring content.