1
Quick scan
Connect external AI clients like ChatGPT and Claude to your workspace context securely using the Model Context Protocol (MCP).
MCP
Requests
Tasks
Approvals
2
Overview
MCP lets compatible external AI clients work with Flopinio context without turning those clients into uncontrolled writers. The current connector is beta, scoped, and approval-aware.
3
What MCP is for
Use MCP when you want an external AI client to read workspace context or stage supported actions against Flopinio records.
4
Current setup model
Workspace owners and admins with agent runtime access can issue MCP tokens from Settings. Add the Flopinio MCP server and bearer token to your compatible client configuration, then restart the client.
5
Write safety
Write-capable behavior stages approvals inside Flopinio. The external AI cannot bypass the approval queue or mutate records silently.
6
Next steps
Read MCP Connector.
Read Grounded Execution.
Common Questions
Is MCP access self-serve right now?
Yes, for workspace owners and admins with agent runtime access. MCP remains beta, and issued tokens can be revoked from Settings.
Can an external AI write directly into my workspace?
No. Supported write actions are staged for approval.
Open the related workspace surface
Use the linked product area after reviewing the page guidance and permission notes.