Flopinio logoFlopinio
Beta Advanced users connecting ChatGPT Apps and external AI clients to Flopinio

MCP And ChatGPT Apps

Connect Flopinio to ChatGPT Apps and compatible MCP clients through scoped reads, staged approval-backed writes, and observable runtime actions.

Explore workflow diagram

Workflow diagram

MCP Connector

MCP Connector as a integration view. The exact controls, permissions, and sequencing should remain in the page text.

System Ready
MCP Connector as a integration view. The exact controls, permissions, and sequencing should remain in the page text.
On this page
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. The shipped surface is scoped reads plus selected approval-backed staged writes; broader tool coverage remains roadmap work.
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.

Keep important external-client actions inspectable inside Flopinio instead of silently mutating records.

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

Roadmap boundary

MCP beta access is not a claim that every workspace action is externally writable, autonomous, or available through every AI client. Additional write coverage, deeper external app behavior, and public API packaging remain roadmap items until shipped and documented.
8

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.

Open agent runs