# Flare

> Projects, meetings, and customer tickets in one system — and Cursor, Claude, and Codex work from the same workspace through MCP.

Flare (https://flares.in) is the operating layer for product teams using AI agents. It keeps projects, customer tickets, and meetings in one context graph so humans and coding agents work from the same memory.

This is flares.in — not the consumer group-chat app named Flare, and not Flare Network.

## Product

- Arlo — Flare's project agent. Turns an idea into a delivery project (epics, stories, acceptance criteria) and keeps status from git. MCP in your IDE.
- Miro — Flare's meeting agent (not miro.com). Calendar, booking, live-call notes. Writes decisions and work back into the graph.
- Kiro — Flare's customer agent (not AWS Kiro). Widget in your product: answers from Flare context, opens tickets with evidence.
- Context graph — projects, tickets, meetings, decisions, and the why, linked.
- MCP — read and write that graph from Cursor, Claude, ChatGPT, and other agents.

## MCP

Hosted Streamable HTTP:

- https://flares.in/api/mcp

Stdio (local):

- npx flare-mcp --token $FLARE_TOKEN

OAuth and token setup live in the app under Settings. Tools cover tickets, meetings, delivery projects, knowledge, and agents. Write tools are scoped; publishing a plan is designed to require a human.

## REST API

Same graph, over HTTP, for anything that isn't MCP-native:

- Base URL: https://flares.in/api/v1
- OpenAPI 3.1 specification: https://flares.in/openapi.json
- Auth: `Authorization: Bearer flr_pat_...` (personal access token, from Settings) or `flr_oat_...` (MCP OAuth token)
- Errors are structured JSON: `{ error: { code, message }, request_id }`

Docs: https://flares.in/developers
MCP story: https://flares.in/mcp
Pricing: https://flares.in/pricing
Trust: https://flares.in/trust

## Optional

- Website: https://flares.in
- Contact: mailto:hello@flares.in