Beta access: FlowOS Local MCP is being tested now. For access notes, feedback, or beta coordination, email [email protected].

Local MCP beta
FlowOS
FlowOS is a by-the-book local MCP server that gives an agent durable records, artifacts, capabilities, actions, and run evidence.
What it does
FlowOS runs next to the agent as a local stdio MCP server. It does not run a model, host your data, or require an Offband account. Goose, Codex, or another MCP-capable client starts the server and calls its tools during normal work.
The server stores state in SQLite under ~/.flowos. Each workspace has its own database, so a local model or agent can keep project memory separate without depending on hosted infrastructure.
Core objects
- Records keep decisions, evidence, issues, notes, standards, and handoffs.
- Artifacts store markdown, JSON, command output, configs, and other useful work objects.
- Capabilities describe reusable procedures an agent can validate and improve.
- Actions define manual, command, or script steps inside a capability.
- Runs preserve execution evidence from using a capability or action.
Bootstrap
Download the local package for your machine, unpack it, initialize a workspace, and point your MCP client at the binary.
Agent bootstrap prompt
Give this to a zero-context agent after adding the MCP command:
Deferred
The public FlowOS skill registry and shared skill marketplace are not part of the current beta. The product focus is the local MCP server, its durable object model, and the agent loop for collecting, running, validating, and refining capabilities.