> ## Documentation Index
> Fetch the complete documentation index at: https://docs.floral.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Build with Floral

> Choose MCP for agent clients or the public API for a stable HTTP integration.

Floral offers two supported integration paths. Both act as a real workspace user, remain pinned to one workspace, and apply current membership, feature, plan, and scope checks.

<CardGroup cols={2}>
  <Card title="MCP" icon="plug" href="/developers/mcp/overview">
    Give an approved agent client a filtered set of Floral tools for questions and actions.
  </Card>

  <Card title="Public API" icon="brackets-curly" href="/developers/api/overview">
    Build a server-side JSON integration against the stable `/api/v1` contract.
  </Card>
</CardGroup>

## Choose MCP when

* a person will use Floral through ChatGPT, Claude, or another MCP client;
* the client can discover tools and call them as part of a conversation;
* the available tool set should follow that user's access automatically.

## Choose the public API when

* your software needs deterministic HTTP requests;
* you need the published OpenAPI schema, idempotency, ETags, and stable error codes;
* your integration uses the currently published company, person, briefing, or summary operations.

The MCP tool set is broader than the public API. Do not call unpublished application routes to fill an API gap. Contact Floral if a required operation is not in the API reference.