RepoFather

RepoFather helps open-source maintainers make a repo easier to understand, try, share, contribute to, and fund.

It scans the files in a repository and returns a practical readiness report: what is already working, what is missing, and which fixes would make the project more launchable.

Quick Start

Most users should start with the CLI. Run this inside any repository you want to score:

npx -p repofather-mcp repofather scan .

Generate launch copy and sponsor-tier ideas:

npx -p repofather-mcp repofather assets .

Return JSON for scripts or automation:

npx -p repofather-mcp repofather scan . --json

Install it globally if you want a shorter command:

npm install -g repofather-mcp
repofather scan .

For local development:

npm install
npm test
npm run build

What It Checks

RepoFather scores five areas:

• Positioning - name, README opening, audience, differentiation, and MCP/OSS positioning.
• Tryability - install command, quickstart, examples, tests, screenshots, or demo links.
• Community - license, contributing guide, issue templates, CI, and roadmap.
• MCP readiness - documented endpoint, tools, client setup, remote deployment, and privacy/security notes.
• Monetization readiness - sponsor path, open-core boundary, hosted/team upgrade path, badges, metrics, or API surfaces.

The output is designed to be fixable. RepoFather does not just say a repo is weak; it tells you what to add next.

Example Output

RepoFather score: 76/100 (Launchable)

Buckets
- positioning: 80/100
- tryability: 75/100
- community: 70/100
- mcp: 90/100
- monetization: 65/100

Strong signals
- One-command install is visible
- License is present
- MCP endpoint/server is documented

Top fixes
- Add a 60-second demo GIF or screenshot
- Add a public roadmap
- Explain the free core vs paid hosted/team features

MCP Server

RepoFather also runs as a remote MCP server:

https://repofather-mcp.nocodepiper.workers.dev/mcp

Use the MCP server when you want an AI client to call RepoFather tools. Use the CLI when you just want a score in your terminal.

Available tools:

• score_repository_snapshot - score a repository snapshot submitted by an MCP client.
• generate_launch_assets - produce launch copy, README badge text, topics, and sponsor-tier ideas.
• monetization_ladder - map an open-core project into free, solo, team, and enterprise layers.

Codex

Codex supports remote streamable HTTP MCP servers directly:

codex mcp add repofather --url https://repofather-mcp.nocodepiper.workers.dev/mcp

Restart Codex after adding the server. Then ask Codex to use RepoFather to score or improve a repository.

Claude Desktop

Add RepoFather to your Claude Desktop MCP config:

{
  "mcpServers": {
    "repofather": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://repofather-mcp.nocodepiper.workers.dev/mcp"
      ]
    }
  }
}

Restart Claude Desktop after saving the config.

Cursor, Windsurf, and Other MCP Clients

Use this command and argument pair in any MCP client that supports stdio servers:

command: npx
args: mcp-remote https://repofather-mcp.nocodepiper.workers.dev/mcp

Some clients ask for JSON instead:

{
  "command": "npx",
  "args": [
    "mcp-remote",
    "https://repofather-mcp.nocodepiper.workers.dev/mcp"
  ]
}

Restart the client after adding the server.

Testing The MCP Bridge Manually

You can test the remote MCP bridge from a terminal:

npx mcp-remote https://repofather-mcp.nocodepiper.workers.dev/mcp

If it prints something like Proxy established successfully between local STDIO and remote StreamableHTTPClientTransport, the connection works.

This command is expected to keep running. It is a bridge for MCP clients, not an interactive CLI. Press Ctrl+C to stop it.

Troubleshooting

npx mcp-remote ... looks stuck

That is normal. mcp-remote starts a local stdio bridge and waits for an MCP client to send requests. It will not print a RepoFather score by itself.

For a terminal score, use:

npx -p repofather-mcp repofather scan .

repofather: command not found

Use the package form:

npx -p repofather-mcp repofather scan .

Or install globally:

npm install -g repofather-mcp
repofather scan .

Which command should I use?

• Use repofather scan . when you want a report in the terminal.
• Use repofather assets . when you want launch copy and sponsor-tier ideas.
• Use the MCP endpoint when you want Codex, Claude, Cursor, or another MCP client to call RepoFather as a tool.
• Use npx mcp-remote ... only when your MCP client needs a local stdio bridge.

Local MCP Development

Run the Cloudflare Worker locally:

npm run dev

Local MCP endpoint:

http://localhost:8787/mcp

Deploy:

npm run build
npx wrangler deploy

Why RepoFather

Useful open-source projects often lose attention for boring reasons: the README does not explain the promise, the install path is unclear, the demo is missing, contributors do not know where to start, or the paid path feels awkward.

RepoFather turns those details into a score and a checklist so maintainers can make the repo more credible before launch, after a rewrite, or before asking people to star, install, sponsor, or adopt it.

Open Core

The CLI and MCP server are open source.

Future hosted features can build on top of the same scoring rules:

• public score pages and badges
• historical score tracking
• private GitHub app scans
• auto-created GitHub issues from failed checks
• launch calendars and saved social drafts
• team policies for release readiness

Roadmap

• 0.1 - CLI scanner, launch asset generator, and remote MCP server.
• 0.2 - GitHub Action and badge JSON endpoint.
• 0.3 - hosted public scan pages.
• 0.4 - private GitHub app scans and score history.
• 1.0 - team dashboards, org policies, and API.

License

MIT