Flopinio logoFlopinio
Flopinio Help Center
Browse guides

MCP, Claude, and ChatGPT apps

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

Beta Advanced users connecting Claude, ChatGPT Apps, and external AI clients to Flopinio
Before you start
  • Active Flopinio workspace membership with AI access
  • Claude, a ChatGPT App, or another MCP-compatible client
Who can use this
  • Public
On this page
Explore workflow diagram

Workflow diagram

MCP, Claude, and ChatGPT apps

Operating loop diagram. The text on this page has the exact steps and permissions.

System Ready
Operating loop diagram. The text on this page has the exact steps and permissions.

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.

Status

MCP access is Beta. Active workspace members with AI access can connect through per-user OAuth or issue their own scoped bearer tokens from Settings. Complete account verification and any requested MFA before connecting. The shipped surface is scoped reads plus selected approval-backed staged writes; broader tool coverage remains roadmap work.

What MCP can do

  • Read scoped workspace context where the token and organization permit access.
  • Search and fetch workspace knowledge through OpenAI-compatible search and fetch tools.
  • 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.

ChatGPT and other browser OAuth clients

Browser OAuth clients discover Flopinio's authorization-server metadata and can register automatically through dynamic client registration (DCR). When connecting through OpenAI's plugin portal, choose DCR if a registration method is offered and use the MCP URL without a shared bearer token. Each workspace user authorizes the connection separately.

  1. 1
    Point the client at https://flopinio.com/mcp.
  2. 2
    Authorize Flopinio in the browser and confirm the selected workspace.
  3. 3
    Review the requested read and write scopes. Tasks, time entries, invoices, approvals, and other tool families use separate permissions.
  4. 4
    Return to the client and verify tools are visible before requesting writes.

Claude web, Desktop, mobile, and Cowork OAuth

Hosted Claude uses https://claude.ai/api/mcp/auth_callback. You need active Flopinio workspace membership with AI access and permission to add a connector in Claude. Flopinio uses automatic dynamic client registration (DCR); Client ID Metadata Document (CIMD) support is not advertised.

  1. 1
    In Claude's connector settings, add a custom connector named Flopinio with the server URL https://flopinio.com/mcp.
  2. 2
    Use automatic OAuth registration. Leave client ID and client secret blank; no shared bearer token is needed.
  3. 3
    Connect and sign in to your own Flopinio account in the browser. Select the intended workspace and complete any requested account verification or MFA.
  4. 4
    Review tool-family scopes and the approval mode before consenting. Each person connects their own account.
  5. 5
    Return to Claude and verify a read, such as fetching a workspace note, before requesting writes.

Claude Code OAuth

Public clients use S256 PKCE without a client secret. Claude Code uses an HTTP loopback callback such as http://localhost:3118/callback or http://127.0.0.1:3118/callback. The listener port can vary, while the registered host, path, and query must match.

  1. 1
    If the Flopinio plugin already provides the server, use that connection and skip adding a duplicate server.
  2. 2
    Otherwise, run this command from your project directory: claude mcp add --transport http flopinio https://flopinio.com/mcp
  3. 3
    Start Claude Code, run /mcp, select Flopinio, and follow the browser authentication flow.
  4. 4
    Sign in, select the intended workspace, review scopes and the approval mode, and verify a read before requesting writes.

OAuth reconnect and revocation

Reconnect from Claude when sign-in expires, a refresh fails, or a tool reports insufficient_scope. Access tokens are short-lived; clients must store the new refresh token returned on every refresh and stop using the previous one. Review the workspace and requested scopes again when reconnecting.

  • Disconnect or remove the server in Claude to stop using that client connection. Removing a plugin or local configuration alone does not prove that credentials were revoked on Flopinio.
  • OAuth clients can submit an access or refresh token to POST /oauth/revoke to revoke that connection's refresh-token family and associated access tokens, including successors of a rotated token. In Settings > Integrations, revoking an OAuth-issued access token also revokes the refresh credentials and associated access tokens for the same OAuth connection. Use Settings if your client does not support token revocation. Separate connections remain usable.
  • Never paste access tokens, refresh tokens, or client secrets into a conversation or shared configuration.
  • Disconnecting does not delete workspace records or existing Flopinio agent-run and approval history. Workspace content returned by MCP is shared with the connected AI client; review that client's data controls and Flopinio's privacy policy at https://flopinio.com/privacy.

Bearer-token setup outline

  1. 1
    Open Settings, then Integrations.
  2. 2
    Issue a named MCP access token and copy it immediately.
  3. 3
    Configure a client that accepts manual bearer tokens, such as Cursor or a CLI tool. Use OAuth for Claude.
  4. 4
    Point the client at https://flopinio.com/mcp and include the bearer token.
  5. 5
    Restart the client and verify tools are visible.

Security note

MCP writes require manual review by default. A token explicitly permitted to self-approve may approve its own eligible writes for the same user and organization. Both paths keep a recorded approval and execution history, and cannot bypass required permissions. Invoice writes and approval resolution need separate permissions. Open Flopinio approvals to inspect and resolve staged changes.

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.

Troubleshooting

If the AI client says "Tool not found", confirm the MCP configuration, OAuth connection or bearer token, workspace, and active tools. For insufficient_scope, reconnect and grant the permission named by the tool. If sign-in fails, reconnect Flopinio in the affected AI client, such as Claude or ChatGPT. If the problem persists, contact support. Never share access tokens or client secrets. A pending or input-required write is expected: complete the offered review form or follow the Flopinio review link to approve it.

Note

Google source restrictions

Google source sections and Google-derived content are unavailable to external MCP clients while their processing route is unreviewed. A Google connection or owner AI consent alone does not authorize an external client. Authored work remains available within ordinary permissions. Historical records that still mix imported Google text with authored work are withheld from external MCP reads until their sources are safely separated. Direct reads return not found, and lists and search omit those records. Ordinary workspace access is unchanged. See Google integrations for the separate consent, sharing, and deletion controls.