Supported MCP clients

Last updated: September 25, 2026

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.

Supported clients

Floxar accepts sign-in from these clients only:

Not supported for sign-in yet

• Cursor does not yet publish the client identity document Floxar needs to accept its sign-in.
• Other MCP clients, including the MCP Inspector and Codex, are not on the list. Floxar keeps this list, and a client that is not on it cannot be enabled for an account.

Automated agents and integrations do not sign in as a person. An account admin registers them in the Floxar application’s Agent Registry, and they connect with their own credentials.

Before you start

• MCP must be turned on for your account. It starts off for every account; ask an account admin to turn it on.
• You need your account URL. Every Floxar account has its own MCP URL, of the form https://mcp.floxar.com/a/<account-id>. Your account admin provides it from the Floxar application. It is the only URL you need, and there are no API keys or tokens to copy.

How connecting works

The first time a client connects, it opens a browser window:

1. Sign in with your usual Floxar login.
2. Confirm the account. The page shows who you are signed in as, the account your account URL belongs to, and that URL. The connection works in that account only.
3. Allow the connection. The page lists what the client will be able to do — read your flows, steps, references and trails; run and update trails on your behalf; create and edit flows and steps — limited to what your account allows MCP clients. Choose Allow, or Deny to stop. A client never gets more than your role allows.

Claude (claude.ai and Claude Desktop)

claude.ai and Claude Desktop share the same connectors. Reading through Claude is confirmed. Running trails and authoring through Claude are not yet confirmed by Floxar.

1. In Claude, open Settings → Connectors and select Add custom connector.
2. Give it a name for the account, such as floxar-acme, paste your account URL, and select Add.
3. Select Connect. Sign in to Floxar in the browser window, confirm the account and allow the connection.
4. In a chat, open the tools menu and make sure the Floxar connector is turned on.

Remote MCP server URL

https://mcp.floxar.com/a/<account-id>

When claude.ai and Claude Desktop use the same connector, one sign-in covers both, and revoking the connection in Floxar disconnects both.

Claude Code

1. Add the server from your terminal. Append --scope user to make it available in every project.

claude mcp add --transport http floxar-acme https://mcp.floxar.com/a/<account-id>

2. Start Claude Code, run /mcp, select floxar-acme and choose Authenticate. Your browser opens so you can sign in to Floxar, confirm the account and allow the connection. You can also run claude mcp login floxar-acme from an interactive terminal.
3. Run /mcp again: the server shows as connected and its tools are ready.

Claude Code asks for every capability when it connects; what it gets is limited to what your account allows MCP clients, and it never acts beyond your role.

VS Code

Connection not yet confirmed by Floxar; the steps follow VS Code’s MCP documentation.

1. Add the server to .vscode/mcp.json in your workspace. If the file already lists servers, add only the Floxar entry inside the existing servers object. Or run MCP: Add Server from the Command Palette, choose HTTP, paste your account URL and give it a name for the account.

.vscode/mcp.json

{
  "servers": {
    "floxar-acme": {
      "type": "http",
      "url": "https://mcp.floxar.com/a/<account-id>"
    }
  }
}

2. Start the server. When VS Code asks to let Floxar sign in, allow it, then sign in to Floxar, confirm the account and allow the connection.
3. Open Copilot Chat in agent mode. Floxar’s tools appear in the tools picker.

More than one account

A connection works only in the account whose account URL you added it with. To work in a second account, add Floxar again with that account’s URL, under a different name — for example floxar-acme and floxar-globex. Each account needs a distinct server name.

Disconnecting and revoking

Removing Floxar from a client does not always end the connection on Floxar’s side:

• Removing the connector in Claude stops Claude from using it, but the connection stays in Floxar.
• claude mcp logout clears only Claude Code’s local sign-in; the connection stays in Floxar.

To end a connection for certain, revoke it in Floxar:

• Your own connections: in the Floxar application, open Profile → Security and select Disconnect applications. This disconnects every AI client you have connected, in every account.
• An account admin can revoke any one connection in the account on the account’s MCP Connections page, or turn MCP off for the account, which revokes every connection in it.

A revoked connection stops working within about 3 minutes. To use the client again, connect it again and allow the connection. Signing out of Floxar, even everywhere, does not disconnect AI clients.

Good to know

• Staying signed in. Your client renews access on its own. After 7 days without use, or 30 days in total, it asks you to sign in again.
• Everything is attributed to you. Actions taken through a connection are recorded under your name, marked as made through MCP, together with the client that made them.
• Adding access later means reconnecting. A connection keeps the capabilities it was allowed with. If it was made read-only and you later want the client to run trails or author, connect again and allow the connection: in Claude Code, run claude mcp logout floxar-acme then claude mcp login floxar-acme (or choose Authenticate again from /mcp); in Claude, disconnect and reconnect the connector in Settings → Connectors. For Claude this is not yet confirmed: when Floxar tested it, Claude asked for read access only, so reconnecting may not add running trails or authoring.
• Your role still applies. A tool that returns PERMISSION_DENIED needs a role you do not have; reconnecting does not change your role.

If sign-in stops

When a connection cannot be made, the Floxar sign-in page says why:

• “MCP connections are not enabled for this account” — ask an account admin to turn MCP on.
• “You are not a member of this account” — the account URL belongs to an account you are not in. Use your own account’s URL, or ask that account’s admin to add you.
• “This account does not allow this client” — the account has restricted which of the supported clients may connect. Connect from one it allows, or ask an account admin. A client outside Floxar’s supported list cannot be enabled for one account.
• “This account allows none of the capabilities the client asked for” — ask an account admin which capabilities MCP clients may have.
• “This account requires a stronger sign-in” — sign in the way the account requires, then connect again.
• An unsupported-client message — connect from one of the supported clients.

For anything else, contact help@floxar.com.