0.1.0

Beta

The first beta of FloConnector.

This is the first beta. It connects your business tools to Claude through hosted MCP endpoints, and it is ready for real work while still moving quickly. If something is rough or missing, tell us at support@floconnector.com.

Connectors

  • A catalog of more than 50 connectors across CRM, marketing, email, accounting, project management and field service.
  • Xero and WordPress are fully native, with tools written against each vendor's API directly. WordPress connects to your own self-hosted site using an application password, so there is no third party in the path.
  • Everything else is delivered through Composio, which manages the OAuth handshake and keeps the tool definitions current.
  • Vendor credentials are envelope-encrypted before they are stored. The database never sees a plaintext token, and Claude never sees a credential at all.

Workspaces, connections and profiles

  • Four levels to structure who can reach what: an account owns workspaces, a workspace owns connections to vendors, and a profile exposes a chosen set of those connections as one endpoint.
  • Profile access is granted per person, so one shared connection can back several endpoints with different scopes for different people. Being an admin is not enough on its own.
  • Roles run from primary owner down to member, and agencies can hold many client workspaces under one account.

MCP endpoints over Streamable HTTP

  • One endpoint per profile, exposing only that profile's tools, namespaced by vendor so the model can tell them apart.
  • Full OAuth 2.1 on the data plane: discovery, dynamic client registration, PKCE, and rotating refresh tokens. Connecting from Claude is the standard flow with no key to paste.
  • Tool results carry structured partial-success ledgers rather than throwing, so a sequence that fails halfway tells the model exactly what completed and what to do next.

Analytics engine

  • Large reads run over a temporary, in-memory analytics workspace. The model sees counts and aggregates; the raw rows never enter its context.
  • The workspace is held only long enough to query what was just read, then discarded after ten idle minutes. Nothing is written to a permanent store.

Metered billing

  • Post-paid metering on external tool calls, on top of the Solo, Pro and Scale plans. Internal calls are logged at zero and shown as included.
  • New accounts get a free grant pool, spent before any metered charge.
  • Credits can also be earned through the rewards program in the dashboard.

Privacy and retention

  • FloConnector is a proxy, not a data warehouse. There is no persistent mirror of your vendor data.
  • The activity log stores metadata about each call, never the arguments or the results, and it is purged after 90 days.
  • Error text coming back from a vendor is redacted before it reaches the model, so an upstream message cannot carry anything unexpected into your conversation.