Agent files
The create command writes the agent guide, the MCP config and the package manifest, so any coding agent works the Startup at once.
npm create startups writes AGENTS.md, .mcp.json and package.json, so any coding Agent works the Startup from cd leaseline with no setup page to find.
leaseline/AGENTS.md.mcp.jsonpackage.jsonREADME.md
Reference
| File | Holds |
|---|---|
AGENTS.md | How a coding agent works this Startup: connect MCP, fetch types, rehearse writes |
.mcp.json | Two MCP servers: https:, scoped to the Startup, and the keyless docs server https: |
package.json | startup-builder and the scripts dev, check, test and deploy |
Examples
Minimal
{
"mcpServers": {
"leaseline": { "url": "https: //api.sb/ mcp? ns= leaseline.app" },
"startupbuilder-docs": { "url": "https: //startupbuilder.dev/ mcp" }
}
}Leaseline
AGENTS.md, as npm create startups writes it. Build with a coding agent reads it line by line.
# Leaseline
This repository defines Leaseline. Its files compile into the running business.
## Before you write
- Connect both MCP servers in .mcp.json.
- Fetch /$.d.ts from the leaseline server: the types of $, cut to your key.
- Read the convention for a file before you change it: https: //startupbuilder.dev/ code/ file-conventions
## While you work
- Keep npx startup-builder dev running. Each save previews as a Change.
- Print a Verb's input with npx startup-builder schema <Noun.verb> before you call it.
- Rehearse every write with --try, or mode "try" in the do tool.
## Never
- Never edit generated/ or .sb/ . Name secrets in env.ts; never write a value.
- Never call Stripe or any outside API directly. Call the Verb.
- Never use --env live. Shipping is Change.review, then the founder's Version.deploy.What it builds
Nothing. The files point agents at the MCP server and the SDK.
Good to know
- Edit
AGENTS.mdfreely; the platform never rewrites it.