MCP.Market

One Person Company OS MCP server

by living-hi·io.github.living-hi/one-person-company-os·v1.0.3·1 stars

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

B70/100grade B
What users say
No reviews yet
Be the first
Safety scan
B70/100

full report

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed One Person Company OS yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

One Person Company OS tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 145 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 70/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How One Person Company OS compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
70/100
higher than 35% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Install One Person Company OS in Claude Code, Cursor or VS Code

claude mcp add one-person-company-os -- docker run -i --rm ghcr.io/living-hi/one-person-company-os-mcp:1.0.3
Add to Cursor

What the publisher says

From the One Person Company OS repository's README, as published. We do not edit it. Read it on GitHub

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/ensurepythonruntime.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.

Nothing above is checked by us. What we check is on the safety report.

One Person Company OS: common questions

Is One Person Company OS MCP server safe?
Mostly: it is graded B (70/100). Read the One Person Company OS safety report
How do I install One Person Company OS?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does One Person Company OS need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is One Person Company OS maintained?
The last commit was 182 days ago (2026-05-06). The latest release is v1.0.3.
How does One Person Company OS compare with other MCP servers?
safety score 70/100 (higher than 35% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.