Build on Focus Flow

Connect Claude & ChatGPT — one click, no code

Focus Flow is an MCP server: your AI assistant can look at your real studio — clients, jobs, calendar, unpaid invoices — and act on it, with your permission. You sign in with your Focus Flow account; there are no keys to copy.

Add to Claude

• In claude.ai: Settings → Connectors → Add custom connector
• Paste the URL: https://focusflowstudio.app/api/mcp
• Sign in with Focus Flow, pick your studio and what Claude may do, approve
• Ask: “What shoots do I have this week?”

Add to ChatGPT

• In ChatGPT: Settings → Connectors → Create (requires a plan with custom connectors)
• Same URL: https://focusflowstudio.app/api/mcp — same Focus Flow sign-in

Claude Code, Cursor & other MCP clients

Headless clients authenticate with a brand API key instead of the sign-in flow. Create one in Settings → Integrations → Focus Flow MCP, then point your client at the same URL with a Bearer header:

# Claude Code
claude mcp add --transport http focus-flow https://focusflowstudio.app/api/mcp \
  --header "Authorization: Bearer ffs_live_..."

# Any MCP client (generic config)
{
  "mcpServers": {
    "focus-flow": {
      "type": "http",
      "url": "https://focusflowstudio.app/api/mcp",
      "headers": { "Authorization": "Bearer ffs_live_..." }
    }
  }
}

The tool list is filtered by the key’s scopes — a read-only key never even sees send_email. 24 tools are exposed: studio overview, client/lead/job search, schedule and availability, gallery stats, unpaid invoices and revenue, price list, plus guarded actions (create lead, update job status, calendar events, email with two-step confirm).

REST API quickstart

Base URL https://focusflowstudio.app/api/v1. Create an API key in Settings → Integrations → Focus Flow MCP (it is shown once — store it like a password), then:

# 1. Verify the key — who am I?
curl https://focusflowstudio.app/api/v1/me \
  -H "Authorization: Bearer ffs_live_..."

# 2. List your clients
curl "https://focusflowstudio.app/api/v1/clients?limit=10" \
  -H "Authorization: Bearer ffs_live_..."

# 3. Create a lead (the API intake for new inquiries)
curl -X POST https://focusflowstudio.app/api/v1/leads \
  -H "Authorization: Bearer ffs_live_..." \
  -H "Content-Type: application/json" \
  -d '{"firstName":"Anna","lastName":"Rossi","email":"anna@example.com","phone":"+39 333 1234567"}'

Authentication & scopes

Every request carries Authorization: Bearer ffs_live_…. A key belongs to one brand: everything you read or write is scoped to that studio — the brandId can never be switched from the request body. Keys are stored hashed, can expire, and are revocable instantly from the panel.

Defaults at creation: all read scopes + crm:write. email:send and bookings:write are explicit opt-ins.

Responses & pagination

Every response uses the same envelope:

// success                                  // failure
{                                            {
  "success": true,                             "success": false,
  "data": { ... },                             "error": "human message",
  "meta": { "nextCursor": "...", "count": 25 } "code": "machine_code"
}                                            }

Lists are cursor-paginated: pass ?limit= (default 25, max 100) and feed meta.nextCursor back as ?cursor= until it comes back null. Cursors are opaque — never build one by hand. Entities are JSON objects in camelCase.

Endpoints

Deliberate boundaries: bookings cannot be created via API (they are born in your public booking page — use POST /v1/leads for intake), lead conversion and job creation stay in the app, and galleries, documents and payments are read-only in v1.

Errors

Rate limits & plans

Watch X-RateLimit-Limit / X-RateLimit-Remaining on every response; a 429 includes Retry-After.

OpenAPI reference

The full machine-readable spec lives at /api/v1/openapi.json (OpenAPI 3.1) — point your generator, Postman or your LLM at it. Prefer it browsable? Open the interactive reference.