fusialDocs

Connect an assistant

Connect to Fusial over Streamable HTTP using OAuth or an API key.

You need a Fusial workspace with an active subscription and an MCP client that supports Streamable HTTP. For browser sign-in, the client must also support OAuth. The server address is:

https://app.fusial.com/api/mcp

Connect with OAuth

  1. Open your assistant's MCP or connector settings and add a remote server.
  2. Name it Fusial and enter the server address above. Choose HTTP or Streamable HTTP if the client asks for a transport.
  3. Start the client's authentication flow. Sign in to Fusial and complete two-factor authentication if required.
  4. Choose the workspace to connect and review the requested permissions.
  5. Approve the connection and return to your assistant.

OAuth connects the assistant as you, for the workspace selected during consent. The assistant's effective access is limited by the requested scopes, the approved grant, and your current workspace role. See permissions for details.

Claude Code

Register the remote server from your terminal:

claude mcp add --transport http fusial https://app.fusial.com/api/mcp

Then open Claude Code, run /mcp, select Fusial, and follow the browser sign-in flow. See the Claude Code MCP documentation for client configuration and authentication options.

Connect with an API key

For clients that accept custom HTTP headers, use a Fusial API key instead of OAuth. An admin can create a key in Settings → API keys. Choose Read-only for queries and reporting, or Full access when the assistant needs to make supported changes.

Configure either of these headers on the MCP connection:

Authorization: Bearer YOUR_FUSIAL_API_KEY
x-api-key: YOUR_FUSIAL_API_KEY

For example, with FUSIAL_API_KEY already set in your shell:

claude mcp add --transport http fusial https://app.fusial.com/api/mcp \
  --header "Authorization: Bearer $FUSIAL_API_KEY"

Use either the OAuth command or the API-key command for this server name. Keep keys private and out of shared configuration files. An API key belongs to the workspace where it was created; it does not follow your active workspace in the browser.

Verify the connection

Ask your assistant:

Call fusial_whoami and tell me which workspace is connected and what access this connection has.

Then try a read:

List the five most recently active contracts in this workspace.

fusial_whoami is available to every authenticated connection. If the workspace or scopes differ from what you expected, fix the connection before asking for changes. The troubleshooting guide covers missing tools and authorization failures.

Workspaces

OAuth authorization binds a client and user to one workspace. To connect that client to another workspace, re-authorize and choose the other workspace. Switching workspaces in the Fusial UI does not switch an existing MCP connection.

For OAuth clients that need an explicit workspace URL, Fusial also accepts:

https://app.fusial.com/api/mcp/o/{orgId}

Replace {orgId} with the workspace ID. This URL must match the workspace already authorized by the OAuth connection; changing the URL does not grant access to a different workspace. API-key connections always use the key's workspace.