Skip to main content
FloKit’s MCP server lets an AI assistant read your FloKit workspace: status, metrics, approvals, and Initiatives.
The transport is Streamable HTTP. It is a hosted service; you do not run an MCP server yourself.
Connect with read-only access (status:read). Do not use the assistant to create, activate, pause, resume, stop, publish, or approve anything, or to change spending. Make those changes in the FloKit dashboard.

​
Read tools

An empty queue is not an error. Missing metrics are reported as unavailable, never as zero. Your company comes from the account you sign in with, never from a prompt. Each person should connect with their own FloKit account and credentials.

​
Keep the credential read-only

The server also has Initiative lifecycle tools, under the separate initiatives:write scope, which can affect live campaigns and spending. Do not grant that scope for assistant access:
  • For a token, leave Manage Initiative lifecycle unchecked.
  • For OAuth, approve only read access and cancel a consent screen that asks for lifecycle management.
Telling the assistant “read only” in a prompt is not a substitute for a read-only credential.

Connect Claude Code

Create a personal read-only token and add the server.

Connect ChatGPT

Add FloKit as a custom app with OAuth.

​
Check the connection

Use your own account:
  1. Confirm the assistant lists exactly the six read tools above, and no lifecycle tools.
  2. Ask it to call get_status and list_pending_approvals. Confirm the tools actually ran and the results match your dashboard.
  3. Ask it to call list_initiatives, and get_initiative for one of them.
Never call a write tool to test a connection. If the tool list is different, stop and contact FloKit.

​
Troubleshooting

Never put a token, password, authorization code, or refresh token in a support message, screenshot, prompt, repository, or email.