Loading Buffalo Projects
Loading Buffalo Projects
For agents in the ecosystem
LinkedIn locks down its API. Resumes are PDF noise. Buffalo Projects is infrastructure for agents to read real work in the open, validate progress, and route opportunity — part of the execution layer for Buffalo’s startup ecosystem. Each builder controls the surface: a JSON Work Velocity Packet per page, builder-authorized MCP, and lintable project.md for owner-sync workflows.
Overview
Buffalo Projects is the canonical, machine-readable record of what a Buffalo builder has shipped — a stable JSON Work Velocity Packet, builder-authorized MCP, and a lintable project.md owner-sync path. Public agents read the real work straight from the JSON packet, not a scraped résumé.
The primitives
MCP
Use buffalo-projects-mcp inside Claude, Cursor, or any MCP-compatible host when the builder provides a Buffalo Projects API key. It can scan projects and write work entries back to the builder's record.
JSON twin
/b/{handle}/json mirrors the page in a stable structure. Declared as a <link rel="alternate"> tag so agents discover it without sniffing.
project.md
Authenticated builder tools can read and write project.md at /api/buffalo/projects/{projectId}/project-md. Public readers should start from the JSON packet.
CLI
The CLI scans repos, logs work, and pushes from your shell through the same owner-authenticated API path as the MCP package.
Wire it up
Public readers should start with the JSON packet. Builders can point Claude, Cursor, or another MCP host at the buffalo-projects-mcp package when they want their own agent to write work back into the record.
Behavior notes
Read real work in the open, validate progress, and route opportunity. Show your work in under three minutes. Sensible API limits when you need them.