solo-founder
# mcp-solo-founder
[](LICENSE)
**Run your one-person company from Claude Code (or any MCP client).** Weekly plans, a markdown CRM, investor update drafts and launch checklists. Everything is plain markdown on your disk. No accounts, no API keys, no cloud.

## Install (one line)
```bash
claude mcp add solo-founder -- npx -y github:Omrigotlieb/mcp-solo-founder
```
Data goes to `./.solo-founder/` by default. To keep one company folder:
```bash
claude mcp add solo-founder -e SOLO_FOUNDER_DIR=$HOME/company -- npx -y github:Omrigotlieb/mcp-solo-founder
```
Other clients (Cursor, Claude Desktop, etc.):
```json
{ "mcpServers": { "solo-founder": { "command": "npx", "args": ["-y", "github:Omrigotlieb/mcp-solo-founder"] } } }
```
## Demo
```text
You: Plan my week. Goals: ship onboarding v2, talk to 5 users, send October investor update.
Claude: → weekly_plan Saved .solo-founder/weekly/2026-W42.md
You: Dana from Acme wants a call Thursday. Add her.
Claude: → pipeline_upsert {name: "Dana", company: "Acme", stage: "call", nextStep: "Thu call"}
You: Draft the investor update. MRR $2.1k (was $1.4k), 38 users.
Claude: → investor_update Draft saved .solo-founder/investor-updates/oct-2026.md (not sent)
```
Resulting files:
```text
.solo-founder/
├── weekly/2026-W42.md
├── pipeline/dana.md
├── investor-updates/oct-2026.md
└── launches/onboarding-v2.md
```
## Tools
| Tool | What it does |
|---|---|
| `weekly_plan` | Up to 5 goals + Friday review section, saved per ISO week |
| `pipeline_upsert` | Add/update a contact (lead → contacted → call → proposal → won/lost), appends to its log |
| `pipeline_list` | Whole pipeline ordered by stage |
| `investor_update` | TL;DR, metrics table with previous values, wins, challenges, asks. Saved as a draft, never sent |
| `launch_checklist` | 10 must-dos for launch day, plus your own items |
## Skills
Agent skills in [`skills/`](skills) that use the tools: `weekly-plan`, `pipeline-review`, `investor-update`, `launch-checklist`. For Claude Code, copy them into `~/.claude/skills/`:
```bash
git clone https://github.com/Omrigotlieb/mcp-solo-founder && cp -r mcp-solo-founder/skills/* ~/.claude/skills/
```
## Develop
```bash
npm install && npm run build && npm test
```
## More from me
- [claude-md-doctor](https://github.com/Omrigotlieb/claude-md-doctor): lint and score your CLAUDE.md out of 100
- [founder-deck-skill](https://github.com/Omrigotlieb/founder-deck-skill): founder notes → HTML pitch deck (agent skill)
- [awesome-claude-skills-gallery](https://github.com/Omrigotlieb/awesome-claude-skills-gallery): see what agent skills produce before installing
- [ai-skills](https://github.com/Omrigotlieb/ai-skills): CLAUDE.md templates, skills, MCP servers and hooks
- [awesome-anthropic](https://github.com/Omrigotlieb/awesome-anthropic): daily-updated Anthropic / Claude resources
If this is useful, a ⭐ helps other people find it.
Built by [Omri Gotlieb](https://github.com/Omrigotlieb). Want this without the terminal? **[Guti AI](https://gutiailabs.com)** is a calm AI workspace for solo founders.
MIT licensed.
> CI workflow is in `ci/github-actions-ci.yml`; move it to `.github/workflows/ci.yml` to enable GitHub Actions.
TDQS
Scored across 5 tools
Each tool produces or manages a distinct artifact type: weekly plan, CRM records, investor update, launch checklist. The only mild overlap is investor_update (a document) versus pipeline_upsert (which also handles investors as records), but the descriptions make the split clear.
Three tools follow a clear resource_action snake_case pattern (pipeline_upsert, pipeline_list, investor_update), but weekly_plan and launch_checklist are bare noun phrases with no verb, so the convention is mixed yet still readable.
Five tools is well within the ideal 3-15 range, and each maps to a distinct founder workflow with no filler.
There are notable gaps: the pipeline has upsert and list but no delete or single-record get, and weekly plans/launch checklists/investor updates are create-only with no way to list or revise existing artifacts. Core creation workflows are covered, but lifecycle operations are thin.