Skip to main content
Read the overview first. This page covers Claude Code.

​
1. Create a read-only token

Sign in to the FloKit dashboard with your own account and open Company → Agent access (owners and admins). Under Create token, enter a Token name you will recognize, such as Claude Code - laptop. Keep Read workspace status selected and leave Manage Initiative lifecycle (activate, pause, resume, stop & hide) unchecked. Select Create token and copy the token. It is shown only once. Check that the new row lists only Read workspace status. Do not share one person’s token with teammates.

​
2. Add the server to Claude Code

These commands are for Bash (macOS, Linux, or WSL). In zsh, run bash first. Use a private terminal.
Keep the JSON in single quotes, so Claude Code saves a reference to the variable rather than the token itself. Claude Code reads the variable from the terminal you start it in, so set it again in each new terminal. Never paste the raw token into a command, a chat, or a committed .env file. If a server named flokit already exists, check it before replacing it.

​
3. Check it works

In Claude Code, open /mcp, select flokit, and confirm the tool list matches the six read tools in the overview. Stop if lifecycle tools appear. Then ask:
Confirm the tools actually ran and the results belong to your workspace.

​
4. Revoke or remove access

To revoke the token, open Company → Agent access, find its row, and select Revoke. Requests with that token then fail. To remove the local configuration:
Removing the local configuration does not revoke the token; revoke it in FloKit as well. Close any running Claude Code sessions too.

​
Claude web app

The token setup above is for Claude Code. The Claude web app uses a custom connector with OAuth sign-in instead. Never paste a FloKit token into an OAuth client-secret field. See the Claude Code MCP documentation for general command reference.