1
Quick scan
Connect Flopinio to compatible AI clients through the current MCP surface for scoped reads, staged approval-backed writes, and observable runtime actions.
Bearer-token auth
Organization scoping
Staged approval-backed writes
Remote triage and invoice actions
2
Overview
The MCP connector lets compatible external AI clients read scoped workspace context and stage selected write-capable workflows through Flopinio's approval-aware runtime model.
3
Status
MCP access is Beta. Workspace owners and admins with agent runtime access can issue and revoke scoped tokens from Settings.
4
What MCP can do
Read scoped workspace context where the token and organization permit access.
Ask for request, task, note, project, and invoice context.
Stage supported write-capable actions through approvals.
Preserve agent run and approval history inside Flopinio.
5
Setup outline
Open Settings, then Integrations.
Issue a named MCP access token and copy it immediately.
Configure your MCP-compatible client, such as Claude Desktop or Cursor.
Point the client at the Flopinio MCP endpoint and include the bearer token.
Restart the client and verify tools are visible.
6
Security note
Write-capable behavior stages pending approvals instead of mutating records immediately. The external AI cannot bypass your required sign-offs. Open Flopinio approvals to inspect and resolve staged changes.
7
Troubleshooting
If the AI client says "Tool not found", confirm the MCP client configuration, token, organization, and active tool definitions. If a write appears pending, that is expected: approve it inside Flopinio.
Open the related workspace surface
Use the linked product area after reviewing the page guidance and permission notes.