English Français العربية

One Person Company OS

Official registry AI and agents

Build and update a visual operating cockpit for AI-native solo founders.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

OCI package ghcr.io/living-hi/one-person-company-os-mcp:1.0.3
Claude Code 
claude mcp add one-person-company-os -e 'PYTHONUNBUFFERED=1' -- docker run -i --rm ghcr.io/living-hi/one-person-company-os-mcp:1.0.3
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "one-person-company-os": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"
            ],
            "env": {
                "PYTHONUNBUFFERED": "1"
            }
        }
    }
}

Environment variables

  • PYTHONUNBUFFERED Keep stdio MCP responses unbuffered.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. One Person Company OS
  2. What You Get
  3. Workspace Model
  4. Safety Boundary
  5. Local Commands
  6. One-Line Install
  7. One-Line Start
  8. Validation

One Person Company OS

English | 简体中文

A visual operating cockpit for AI-native solo founders.

One Person Company OS helps one founder turn an AI product idea into a company that can be inspected, advanced, and handed off between sessions. It keeps the business loop visible:

promise -> buyer -> product capability -> delivery -> cash -> learning -> asset

The first workspace is built around the questions a solo founder actually needs to answer today:

  • What promise can I sell?
  • Who is the first buyer?
  • What is the current bottleneck?
  • Which arena needs the next push: sales, product, delivery, cash, or assets?
  • What is the shortest action I can take today?
  • Which files were actually saved inside my approved workspace?

What You Get

  • a local operating cockpit you can open after download
  • editable markdown work surfaces for the founder and role agents
  • numbered DOCX deliverables for formal handoff
  • deterministic SVG visuals for the business loop and revenue pipeline
  • role briefs, reminders, flow notes, and starter deliverables aligned to the same operating loop
  • optional AI-image prompts for covers, launch posts, and promotion

Workspace Model

Generated workspaces use three output layers:

  • HTML reading layer for first-pass review and navigation
  • Markdown work layer for ongoing editing and agent collaboration
  • DOCX deliverable layer for formal outputs under artifacts/ or 产物/

Chinese founders get:

  • 阅读版/00-经营驾驶舱.html
  • 视觉素材/business-loop.svg
  • 视觉素材/revenue-pipeline.svg
  • 视觉素材/ai-image-prompts.md

English founders get:

  • reading/00-operating-cockpit.html
  • visual-kit/business-loop.svg
  • visual-kit/revenue-pipeline.svg
  • visual-kit/ai-image-prompts.md

The hidden machine state stays at .opcos/state/current-state.json.

Safety Boundary

  • script mode expects an existing local Python 3.7+
  • scripts/ensure_python_runtime.py prints compatibility and manual install guidance only
  • the marketplace build does not auto-install system packages
  • generated files stay inside the founder-approved workspace directory
  • normal use does not require API keys or unrelated credentials
  • AI images are optional creative assets, not a required runtime dependency

Local Commands

python3 scripts/preflight_check.py --mode create-company
python3 scripts/ensure_python_runtime.py
python3 scripts/init_business.py "North Star Lab" --path ./workspace --product-name "North Star Assistant" --target-user "independent builders" --core-problem "they need one visible loop for product, revenue, delivery, and cash" --product-pitch "a visual operating cockpit for one-person AI companies" --language en-US --confirmed
python3 scripts/validate_release.py

One-Line Install

clawhub install one-person-company-os

One-Line Start

I am building a one-person AI company. Use one-person-company-os v1.0. First help me confirm the sellable promise, first buyer, and core problem. Then create the approved local workspace, open with the operating cockpit, show the current bottleneck visually, and save only approved files inside that workspace.

Validation

python3 scripts/validate_release.py

It validates the state model, localized workspaces, operating cockpit, visual assets, DOCX-only artifact directories, role/template language, and public release materials.

Frequently asked questions

What is One Person Company OS?

Build and update a visual operating cockpit for AI-native solo founders.

How do I install One Person Company OS?

It runs on your machine. In Claude Code: claude mcp add one-person-company-os -e 'PYTHONUNBUFFERED=1' -- docker run -i --rm ghcr.io/living-hi/one-person-company-os-mcp:1.0.3. For other clients, paste the JSON configuration from this page into their MCP settings.

Does One Person Company OS need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is One Person Company OS open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains One Person Company OS?

It is published by living-hi. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.