Day 25: MCP integration — running the framework from your editor

Six tools, one MCP server, zero context-switching out of your IDE.

Yesterday

Yesterday you built the share template. Today you collapse the manual procedure into an editor command.

Why this signal matters

After 24 days of running the manual procedure, the integration buys back the time. The MCP server exposes the same six signals as IDE-callable tools — score an org from Claude Desktop, Cursor, or Windsurf in a single command. The framework you now own becomes editor-native.

The 5-minute exercise

1Install the MCP server (free): the install card on /install has the one-line config for Claude / Cursor / Windsurf.
2Test by asking the model: 'score the github org [name] using the composite framework.'
3Verify the response matches a manual run within ±0.5.
4Add the score-an-org command to your editor command palette.

What you’re filtering for

A working MCP integration that returns a composite + signal breakdown for any public GitHub org in <5 seconds. If installation fails, the issue is almost always the editor's MCP config syntax — the install page has the exact JSON for each editor.

Edge case

If you don't use a model-augmented editor, skip this day — the manual cadence still works. The MCP layer is the speed unlock, not a prerequisite.

Bonus

Once the MCP works, you can run the framework on a founder's GitHub during a Zoom call without leaving the editor or the call. The diligence move that used to take 25 minutes pre-meeting now happens during the meeting.

Tomorrow

Tomorrow: customising the composite weights — the framework is yours, you should weight it like yours.

Curriculum: /challenge · Methodology: /methodology · Paper: ssrn.com/abstract=6606558