The logic layer for agents and developers

Flowmaps maps every path through your codebase in plain language and keeps it current as the code changes. Everyone on your team, and every agent you use, works from the same picture of how things work.

Install the GitHub App
$claude mcp add --transport http flowmaps https://mcp.flowmaps.dev
acme/shop/Place an order ✓ 6/6 verifiedmain@a91f3c2

Flows · 38

HTTPPlace an order
HTTPCancel an order
QUEUERetry a payment
HOOKHandle a Stripe refund
RPCGet inventory
CRONSend nightly payouts
GQLQuery order history
CLIBackfill tax rates
HTTPApply a coupon
QUEUEIndex a product
+ 28 more
HTTP Place an order Charge the cart and record the order. POST /v1/orders
routessrc/routes1
billingsrc/billing3
storesrc/db2
POST /v1/ordersTriggerHTTP
1Stop if the cart is emptyorders.ts:31–36Decision
If the cart is empty
409 Cart is empty
2Price the cartprice.ts:40–77Compute
3Charge the cardcharge.ts:30–44Call
If the card is declined
4Release the cart holdcharge.ts:47–52Write
402 Payment required
5Write the orderorders.ts:88–120Write
6Queue the receipt emailoutbox.ts:12–29Enqueue
201 Order created
Synced on merge38 flows · 214 stepsLast trace 4 min agoMCP · 3 agents connected
Used by teams at
Panther
Features

Know what your code does, and what every change does to it

Flowmaps keeps a live map of every path through your code, shows how each pull request changes that logic, and gives every agent the same map over MCP.

Live map

A living map of your code

Every path through your codebase, drawn as steps you can follow from trigger to outcome. It redraws itself as the code changes.

Pull requests

See what a change does, not just what it touches

Each pull request shows how the logic changes, step by step, so you don't have to read the diff line by line to know what it does.

Agents

One shared understanding for every agent

Every agent in your repo reads the same map over MCP, so they all start from what the code actually does instead of working it out again from the files.

The logic layer

A shared understanding of your code, for every agent

Without a shared map, each agent rereads the repo and builds its own picture. With Flowmaps, it asks the map and reads only the lines that matter.

Three agents ask the same question: How does checkout handle a declined card?

Trust

Why your agents can rely on it

Discovery in any language

An agent finds entry points the way a new engineer would. Framework recipes pin down the common ones exactly.

TypeScriptGoPython

Every step points to the code

Each step links to the file and lines that run it, so you can check any claim in one click.

Evidence is a path, lines, a commit and a hash

Verified, or marked unresolved

A second pass checks each step against the cited code. What it can't confirm is flagged, never filled in.

Confirmed, partial or unresolved

Updated on every merge

Flows a merge touches are re-checked and carried to the new commit. Anything out of date is marked stale.

2 flows carried from a91f3c2 to 7d0e1b4

Stay in touch with your codebase

Map a repo, connect your agent, and see what your next pull request changes.