Stop hunting for context, it is already in the cockpit.
Bolt five vendor servers onto your assistant and it gets five disconnected views. FlowPilots is built to give it one: your tools already joined up, and the next move already staged. The server is planned; nothing on this page is live yet.
ONE ENDPOINT, EVERY CLIENT
Paste once, when it ships, and your assistant sees FlowPilots as tools it can reason about. Built for MCP clients such as:
Not a wall of text, the actual instrument.
The tool result is designed to carry its own panel. Ask the sample one.
ANY MCP CLIENT
Three things, and one of them is costing you a clean purchase count.
GA4 purchase event missing from /checkout/confirm since Tuesday. Two meta pixels returning 403. Tag audit: 48/50 passing.
A client that cannot draw panels will still get the answer as text.
Saved panels, instant recall.
Customize a panel, save it to your Rack, and any assistant will open it by name. Your morning pacing check, your tracking dashboard, your approval queue: one word away.
Reading is free, moving is earned.
The planned split: free reads; Pro stages, approves, and keeps the record. Every Wing adds its own tools to the same server.
Read tools are flagged read-only. Write tools never execute: they hand back a staged move, the same gate the cockpit runs today.
A new front door does not mean a new back door.
A chat window changes where you stand, not what the product may do.
Your credentials stay in the cockpit. The MCP surface is built to see tool results, never keys or tokens.
Every View is designed to run in a sandbox: no DOM, no cookies, no storage, no undeclared network.
Every call, approval, and outcome lands on the audit trail the cockpit already keeps.
FOR DEVELOPERS
Connection: { "mcpServers": { "flowpilots": { "url": "the address, when the server ships" } } }
Tools declare _meta.ui.resourceUri pointing to a ui:// resource. Hosts render Views in sandboxed iframes. CSP metadata declares allowed domains. Display modes: inline, fullscreen, pip.
MCP in every cockpit, the whole of it in Pro.
| Capability | FREE | PRO |
|---|---|---|
| Cockpits reachable | This cockpit | Every cockpit you hold |
| Tools on the server | 5 read tools | All 12, plus every Wing you fly |
| What it can do | Read and report | Read, stage, approve, record |
| Inline panels | Stock set, read-only | Full set, customizable |
| Save to your Rack | Stock panels only | Your own, unlimited |
| Display modes | Inline | Inline, fullscreen, pip |
The plan: MCP included in Pro at no extra charge, and the read-only scope above on free cockpits. One address will cover every cockpit on the account, which is how an agency would reach all of its clients from one place. Limits are provisional until billing opens.
Link your tools once. The cockpit handles auth and keeps your credentials.
When the server ships, copy its address into any MCP-capable assistant. One URL, every tool.
Your assistant will see FlowPilots instruments as tools it can reason about.
One server, every assistant.
The server is planned. The cockpit is free.