One Person Company OS
Mount your founder workspace and let an agent maintain a visual operating cockpit—goals, queues, and company OS artifacts—for a one-person AI-native business.
Overview
One Person Company OS is an MCP server for the Build phase that updates a founder’s mounted workspace into a visual AI-native operating cockpit.
What is this MCP server?
- Stdio MCP packaged as OCI ghcr.io/living-hi/one-person-company-os-mcp
- Bind-mount a founder-approved local workspace into /workspace in the container
- Targets AI-native solo founders building a durable one-person company OS
- PYTHONUNBUFFERED=1 for reliable stdio MCP streaming
- Version 1.0.3 server schema aligned with the One Person Company OS repo
- Published MCP image tag one-person-company-os-mcp:1.0.3
- Server schema version 1.0.3
- Single required runtime argument pattern: bind mount workspace to /workspace
Community signal: 1 GitHub stars.
What problem does it solve?
Solo founders lose coherence when plans, metrics, and tasks live in chats instead of a single agent-addressable operating surface.
Who is it for?
Indie builders who run the business from a repo or folder tree and want MCP-driven cockpit maintenance with Docker.
Skip if: Teams needing multi-tenant SaaS PM, or anyone unwilling to mount a local workspace into a container.
What do I get? / Deliverables
Your agent reads and updates cockpit artifacts inside an approved workspace mount, giving you a persistent one-person company OS.
- Mounted /workspace accessible to MCP tools
- Updated visual operating cockpit files in the founder workspace
- Repeatable agent workflow for OS refresh cycles
Recommended MCP Servers
Journey fit
The product is the operating system for how you run the company; that lands in Build while you shape how you ship and track work. PM is the shelf for cockpit layouts, operating rhythms, and founder dashboards rather than customer-facing frontend code.
How it compares
Founder workspace cockpit MCP, not a third-party Notion or Linear integration.
Common Questions / FAQ
Who is One Person Company OS for?
AI-native solo founders who want a visual operating system maintained inside their own workspace via MCP.
When should I use One Person Company OS?
While building your operating rhythm and PM artifacts—after you have a workspace path you are willing to expose to a mounted MCP container.
How do I add One Person Company OS to my agent?
Pull ghcr.io/living-hi/one-person-company-os-mcp:1.0.3, pass --mount type=bind,src={workspace_path},dst=/workspace, register stdio MCP in Claude Code or Cursor, and set PYTHONUNBUFFERED=1.