Skip to main content
A workspace administrator must enable assistants under Settings > Workspace > Name and rules before an MCP connection can use Floral. See Floral in other apps to manage your personal connections. Every client uses the same server address:
The Settings > Account > Floral in other apps page in Floral shows the same steps with the address of your deployment filled in.

Connect with OAuth

Use OAuth when your MCP client supports remote server sign-in. Floral asks you to sign in and choose an eligible organization and workspace, then shows the read and write disclosure. The connection receives the same available tools as the in-app Assistant, subject to your current permissions.
1

Add the server

Run this in your terminal:
2

Approve access

Approve access in the browser window Claude opens. Floral is then available in every Claude Code session on this machine.
After you connect, the connection appears under Settings > Account > Floral in other apps, where you can disconnect it. If the client cannot start or complete the sign-in flow, use a personal access token if it supports custom headers, or contact Floral. OAuth connections created before write access was introduced remain read-only. Reconnect the client to review and grant read and write access.

Connect with a personal access token

1

Open Floral in other apps

In the target workspace, open Settings > Account > Floral in other apps, open Advanced, and select Create key.
2

Choose access

Give the key a recognizable name, select the smallest required scopes, and choose 30 days, 90 days, one year, or no expiry.
3

Copy the key

Copy it when Floral displays it. The full value is shown once.
4

Configure the client

Use the MCP server URL and send the key as a bearer token:
Client configuration formats differ. Use the client’s current documentation to set a custom header. Revoke the key in Floral when the client is retired or the key may have been exposed.