Start

Quickstart

Point your agent at Flow, make a project, and run the whole loop once. About five minutes.

Flow is a remote MCP server. There is nothing to install and no key to generate first: your client registers itself, and you sign in with a code mailed to your address. There is no password, and no separate sign-up; redeeming your first code creates the account.

1. Add the server

In Claude Code:

claude mcp add --transport http flow https://flow.ttoss.dev/mcp

In Claude, on the desktop or the web: Settings → Connectors → Add custom connector, with https://flow.ttoss.dev/mcp as the URL.

In Cursor, in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "flow": {
      "url": "https://flow.ttoss.dev/mcp"
    }
  }
}

In VS Code, in .vscode/mcp.json:

{
  "servers": {
    "flow": {
      "type": "http",
      "url": "https://flow.ttoss.dev/mcp"
    }
  }
}

Any other client that speaks MCP over streamable HTTP takes the same URL.

The first time the client connects, it opens a consent screen in your browser. Sign in with the code, and choose which of your projects this client may reach. A client restricted to some projects never sees the others, and reaches your inbox only if you also tick Inbox — the inbox is in no project, so choosing projects cannot grant it.

An agent that runs unattended, such as CI or a scheduled job, cannot click through a consent screen. Give it an API key of its own instead, from the console at /app.

2. The method comes with it

The tools say what Flow can do. The method says when to do it and whose decision it is. An agent without the method still captures and closes work, but it also triages your inbox into commitments on its own and closes tasks without saying why.

Flow sends the method as the server’s instructions in the same handshake that hands over the tools, so a client that surfaces server instructions has it from the first turn. If yours does not, or you want to add standing rules and a default project, paste the same block into your project’s CLAUDE.md or AGENTS.md.

3. Make a project

A Flow project is where work lives and who can see it. Make one per thing you work on. Say:

“Create a Flow project called Billing.”

The agent calls create-project and gets back a proj_… id. Every later write names it. If this repository always belongs to that project, say so in CLAUDE.md (“Work in project proj_… unless told otherwise”) and you will not be asked again.

4. Run the loop once

Say these to your agent, in order:

“Capture: the invoice PDF renders the wrong currency for EU customers.” The agent calls ingest-capture. Nothing is decided yet, and nothing should be.
“What’s in my inbox? Propose what to do with each.” The agent reads list-captures and proposes a status, a project and a first action for each item. It writes nothing until you answer.
“Yes to the first, make it active.” The agent calls triage-capture. Now it is a commitment, because you said so.
“What should I work on?” The agent calls get-next and shows you the one task at the top of the ready set. Ask for more if you want to choose.
“Let’s stop here.” The agent writes back what the run produced and tells you in one line what it wrote.

That is the whole loop at its smallest.

How Flow works: what Flow keeps, and what it computes on every read.
Sessions: the phrases for starting a day, ending one, and the weekly review.
Principles: why each step is shaped the way it is.

Quickstart

1. Add the server

2. The method comes with it

3. Make a project

4. Run the loop once

Next