# Flare — The workspace for product teams and AI agents

> Flare brings projects, meetings, and customer tickets into one system — and gives Cursor, Claude, and Codex the context to work from it.

Start a workspace (no sales call): https://flares.in/login?mode=signup

## The problem

Your context lives in ten places — Notion, Linear, Zoom, Intercom, Slack, Jira — and your agents can't read any of them. Flare already knows all of it: one workspace, and MCP for every agent you use.

## The product: one workspace, three surfaces

### 01 · Arlo · Projects — Plan and ship
Turn an idea into epics and stories in shipping order. Track what's blocked and why. Done means merged.
- Turns a sentence into a plan: epics, stories, and acceptance criteria, ordered by what should ship first.
- Tracks blockers explicitly — every dependency shows up as "waiting on X."
- Completion comes from git — when the PR merges, the story closes.
- Queryable from your editor — Cursor, Claude, and ChatGPT ask Flare what's next, instead of guessing.

More: https://flares.in/arlo

### 02 · Oren · Meetings — Capture decisions
Every call becomes decisions, tickets, and requests — with the line from the transcript attached.
- Decision vs. discussion: confirmed decisions write into the project; everything else stays parked.
- Bugs and requests become real tickets, with the transcript line attached.
- Every meeting builds on the last — the next call opens with what's still open.
- Nothing ships without approval — Oren drafts the work, you confirm what goes in.

More: https://flares.in/miro

### 03 · Nori · Customers — Answer and triage
An AI agent on your product that answers from your docs, or files a bug with the screenshot attached.
- Answers from your knowledge, not a generic model.
- Files bugs with evidence: screenshot, browser version, exact page.
- Stages feature requests, never promises them.
- Customers never see your backlog — Nori is the front desk, the ticket is yours.

More: https://flares.in/kiro

## Why one workspace matters

Every surface writes into the same context. A decision on Tuesday's call is on the project by Tuesday afternoon. When the same customer hits the same bug on Thursday, the ticket already exists.

## Built for the whole product team

- **Product** — Ideas that don't die in Notion. Arlo decomposes the idea before anyone codes; Oren catches the decision that would have vanished; the why stays on the story.
- **Engineering** — Agents that actually know your project. Cursor and Claude query the backlog through MCP; done means merged, not "looks tidy"; bugs arrive with evidence.
- **Customer success** — Answer the customer, or file the bug. Nori answers from your docs; a dead button becomes a ticket with the screen; a feature ask is staged, never promised.

## Getting started

1. Paste your website — the one your customers use, not a deck or a doc.
2. Flare reads the product — who you sell to, what it does, what's on the page becomes the starting memory.
3. Connect your agents — Cursor, Claude, Codex, and ChatGPT read and write to the same workspace through MCP.

## Questions

- **What is Flare?** Projects, meetings, and customer tickets in one system — and Cursor, Claude, and Codex work from the same workspace through MCP.
- **What is Flare MCP?** The Flare Model Context Protocol (MCP) server connects AI coding assistants—including Cursor, Claude, Claude Code, and Codex—to the live Flare workspace so they can read projects, tickets, and meeting decisions and write updates without pasting the company back in. Install with `npx -y flare-mcp` or https://flares.in/api/mcp.
- **How do AI agents connect?** The Flare MCP server at https://flares.in/api/mcp. Connect once from Cursor, Claude, Claude Code, or Codex.
- **Do I need a sales call?** No. Create a workspace at https://flares.in/login?mode=signup.
- **Is this the group-chat app or Flare Network?** No. flares.in is Flare, the workspace for product teams and AI agents.

## MCP — give every agent the context it needs

Connect Flare once. Cursor, Claude, Codex, and ChatGPT can then read tickets, plan projects, log meetings, and update stories — from the tool you already work in.

- **From the editor** (Cursor, Claude Code, Codex) — pull the tickets that exist, ask what's next on the project, write back without leaving the editor.
- **From the chat** (Claude, ChatGPT) — create and run the project, file the meeting not the vibe, stage tickets from the ask.

Full MCP story: https://flares.in/mcp

---
Site map: https://flares.in/sitemap.xml · Machine-readable summary: https://flares.in/llms.txt · API: https://flares.in/openapi.json · Docs: https://flares.in/developers