oci ghcr.io/living-hi/one-person-company-os-mcp:1.0.3stdioMITupdated 4mo ago
A visual operating cockpit for AI-native solo founders.
What can you do with One Person Company OS?
One Person Company OS
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.htmlvisual-kit/business-loop.svgvisual-kit/revenue-pipeline.svgvisual-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.pyprints 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.
Install
Add One Person Company OS to your client. Pick the one you use.
claude mcp add ghcr-io-living-hi-one-person-company-os- -- docker run -i --rm ghcr.io/living-hi/one-person-company-os-mcp:1.0.3codex mcp add ghcr-io-living-hi-one-person-company-os- -- docker run -i --rm ghcr.io/living-hi/one-person-company-os-mcp:1.0.3amp mcp add ghcr-io-living-hi-one-person-company-os- -- docker run -i --rm ghcr.io/living-hi/one-person-company-os-mcp:1.0.3{
"mcpServers": {
"ghcr-io-living-hi-one-person-company-os-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"ghcr-io-living-hi-one-person-company-os-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
code --add-mcp '{"name":"ghcr-io-living-hi-one-person-company-os-","command":"docker","args":["run","-i","--rm","ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"]}'Or add the block manually to `.vscode/mcp.json` under `servers`.
{
"mcpServers": {
"ghcr-io-living-hi-one-person-company-os-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"ghcr-io-living-hi-one-person-company-os-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"ghcr-io-living-hi-one-person-company-os-": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"ghcr-io-living-hi-one-person-company-os-": {
"type": "local",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"ghcr-io-living-hi-one-person-company-os-": {
"command": {
"path": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"
]
}
}
}
}Add to your Zed `settings.json`.
docker run -i --rm ghcr.io/living-hi/one-person-company-os-mcp:1.0.3Run `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation17/25
- Maintenance13/25
- Trust13/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 118 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 12 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 1.0.3Latest | May 6, 2026 |