solo-founder
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOLO_FOUNDER_DIR | No | Directory where company data (weekly plans, pipeline, investor updates, launch checklists) is stored. Data goes to ./.solo-founder/ by default; set this to keep one company folder. | ./.solo-founder/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| weekly_planC | Create this week's plan (top goals + Friday review) as markdown. |
| pipeline_upsertC | Add or update a customer/investor in the local markdown CRM, appending to its log. |
| pipeline_listA | List everyone in the pipeline, ordered by stage. |
| investor_updateC | Draft a monthly investor update (TL;DR, metrics table, wins, challenges, asks). |
| launch_checklistC | Create a launch checklist for a product. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.