Flare
Get started
Menu
WhyUse casesArloMiroKiroAgentsContextMCPPricingLog in

Projects · Meetings · Customers

The workspace forproduct 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.

No site yet? Start empty

↓ One scroll

The problem

Your context lives in ten places. Your agents can’t read any of them.

What you paste into Cursor · againWe're a B2B product. Tuesday Priya said
ship referrals without waiting on billing.
Sam was only considering a waitlist.
Safari still drops focus on checkout.
We killed waitlists in March because
enterprise couldn't support them.

What's the first epic?
Flare already knows all of it.

Notion, Linear, Zoom, Intercom, Slack, Jira — one workspace, and MCP for every agent you use.

The product

One workspace. Three surfaces.

Projects, meetings, and customer conversations — connected, and readable by your team and every agent you use.

01 · Arlo · ProjectsPlan and ship

Turn an idea into epics and stories in shipping order. Track what’s blocked and why. Done means merged.

See how it works →02 · Miro · MeetingsCapture decisions

Every call becomes decisions, tickets, and requests — with the line from the transcript attached.

See how it works →03 · Kiro · CustomersAnswer and triage

An AI agent on your product that answers from your docs, or files a bug with the screenshot attached.

See how it works →

01 · Projects

Arlo

Plan the work, in the order it should ship.

Flare breaks an idea into epics and stories, marks what’s blocked, and tracks completion from the git branch — so your team and your agents work from the same plan.

  • Turns a sentence into a planEpics, stories, and acceptance criteria, ordered by what should ship first.
  • Tracks blockers explicitlyEvery dependency shows up as “waiting on X.” No hidden order-of-operations.
  • Completion comes from gitWhen the PR merges, the story closes. No manual status updates.
  • Queryable from your editorCursor, Claude, and ChatGPT ask Flare what’s next, instead of guessing.
See how Arlo plans a project →
You
ArloFour epics. Start with the first two. The others depend on them.
Epic 01 · readyReferral ProgramWho can invite. Who gets paid.
Epic 02 · readyTrackingUnique links. Attribution that isn’t a vibe.
Epic 03 · blocked on 01RewardsDepends on Program. Don’t start here.
Epic 04 · blocked on 02AnalyticsDepends on Tracking. Ship after.
INV-12 Invite flowmerged
ONB-4 Empty statePR open
ONB-9 Rewardsblocked on Program

02 · Meetings

Miro

Every meeting leaves work behind.

Miro joins the call, separates decisions from discussion, and files the tickets, bugs, and requests that came up — into the same workspace your projects live in.

  • Decision vs. discussionConfirmed decisions write into the project. Everything else stays parked.
  • Bugs and requests become ticketsNot action items in a doc. Real tickets, with the transcript line attached.
  • Every meeting builds on the lastThe next call opens with what’s still open from the previous one.
  • Nothing ships without approvalMiro drafts the work. You confirm what goes in.
See how Miro runs a meeting →

What was said

Priya

Let’s ship referrals without waiting on billing.

Decision
Sam

We’re considering a waitlist — not committing.

Not a decision
Dev

Safari still drops focus on checkout.

Bug
Alex

Customers keep asking to export the report themselves.

Request

What Miro filed

Decision · PriyaShip referrals. Billing can wait.Written to the Referral Program project.
Parked · SamWaitlist — considering only.Not a story until someone decides.
Bug · Safari 18Checkout drops focusFiled with the transcript line attached.
Request · stagedSelf-serve exportThree customers asked. Waiting on your call.

03 · Customers

Kiro

A support agent that lives on your product.

Kiro answers customer questions from your docs and product context — and when it can’t, it files a ticket with the screenshot, browser, and page attached.

  • Answers from your knowledge, not a generic modelYour docs, your product, your decisions — not a stock chatbot.
  • Files bugs with evidenceScreenshot, browser version, exact page. Engineering doesn’t have to ask.
  • Stages feature requests, never promises themThree customers asked for scheduled export — it becomes a request on the project, not a commitment in chat.
  • Customers never see your backlogKiro is the front desk. The ticket is yours.
See how Kiro handles a customer →
acme.app / settings / team

Your product

Invite teammates

They get a link. Roles come later.

Invite
Kiro · on your product
How do I invite my teammates?
KiroSettings → Team → Invite. They get a link. If it lands in spam, resend from the same row.
The Invite button doesn’t do anything.
KiroConfirmed — dead after click. I grabbed the screen.
Evidence · Safari 18
Invite
Bug · filed for engineeringInvite button does nothingScreenshot, browser, and page attached. Customer never sees the backlog.

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.

Tuesday · Meeting
Decision: ship referrals. Billing waits.Sam’s waitlist stays parked. The Safari bug leaves the call as a ticket.
Tuesday · Project
Referral Program: 4 epics, 2 ready.Decision attached. Blockers listed. Cursor knows what’s actually next.
Thursday · Customer
Acme hits Safari checkout — third report this quarter.The ticket is already open, with Tuesday’s transcript line on it.

Built for the whole product team

One workspace. Three roles.

Product

Ideas that don’t die in Notion.

Turn a sentence into a shipping plan. Meetings that produce tickets, not action items. The “why” stays on the story.

  • Arlo decomposes the idea before anyone codes.
  • Miro 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. Bugs come with screenshots. Done means merged, not “looks tidy.”

  • MCP: what’s blocked, what’s next, which ticket has the screen.
  • Done means merged, not marked.
  • Bugs arrive with evidence, not a Slack thread.

Customer success

Answer the customer, or file the bug.

Kiro handles the “how do I…” volume. Real bugs turn into tickets with evidence. Requests get staged — never promised.

  • Kiro answers from your docs, on your product.
  • A dead button becomes a ticket with the screen.
  • A feature ask is staged — never promised in chat.

Getting started

Start from your website. Be running in a minute.

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

04 · Model Context Protocol

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.

CursorClaude CodeCodexClaudeChatGPT
CursorClaude CodeCodex

Engineering · via MCP

From the editor

You’re already in the repo. Ask Flare what’s next, what’s blocked, and which bug has the screenshot — then ship. The agent reads the workspace, not a prompt you typed this morning.

  • Pull the tickets that existOpen checkout bugs, with the screenshot attached. Not a Slack thread from Thursday.
  • Ask what’s next on the projectStories in order. What’s blocked and why. Rewards still waits on Program.
  • Write back without leaving the editorComment, link the PR, close the story. Flare already knows the context.
In Cursor · via MCP

Give me the open checkout bugs and what’s next on Referral Program.

Bug · Safari 18 · AcmeCheckout drops focusScreenshot attached. Tuesday’s line is on the ticket.
Story · INV-12 · readyInvite flowFirst epic. Start here.
Blocked · ONB-9RewardsWaits on Program. Don’t start here.
ClaudeChatGPT

Product · via MCP

From the chat

You’re not in the codebase. You’re in the work. Create the project, file the meeting, stage the ticket — from the chat you already live in. Flare writes it. Engineering can query it later.

  • Create and run the projectA sentence becomes epics. Move them, block them, ask what’s slipping — without opening a board.
  • File the meeting, not the vibePriya confirmed. Sam was only considering. One writes to the project. The other stays parked.
  • Stage tickets from the askThree customers want export. That’s a request on the project — not a promise in ChatGPT.
In Claude · via MCP

Create a project for referrals. Priya said ship it — billing can wait. Stage the Safari bug from the call. Park Sam’s waitlist.

Arlo · project ONBReferral ProgramFour epics. Two ready. Two blocked.
Miro · TuesdayShip referrals. Billing can wait.Waitlist stays parked. Not a story.
Kiro · stagedSafari checkoutFiled from the call. Waiting on engineering.

The whole loop

A full loop, in one afternoon.

  1. 01 · MCPClaude
    PM asks Claude to spin up a project for referrals.Arlo writes four epics. Rewards is blocked on Program. The why is on the story.
  2. 02 · MCPChatGPT
    After the call: file Tuesday. Sam was only considering a waitlist.Miro writes the decision. The waitlist stays parked. Safari leaves as a ticket — with the transcript line.
  3. 03 · MCPCursor · Codex
    Engineer pulls the open bugs and the next stories.INV-12 is ready. Rewards is not. Acme’s Safari ticket comes with the screenshot.
  4. 04 · GitMerged
    The PR merges. The story closes. Done means merged.The next prompt doesn’t need the company pasted back in. Flare already has it.
Connect MCP in two minutes →

Ready when you are

Start from your website.

No site yet? Start empty