Launch your product from the terminal: NLB CLI + MCP
You do not need a web form to launch on Next Level Builders. The open-source directory toolkits give you a CLI for your terminal and an MCP server for your agent, both MIT licensed.
1. Start from a template
There are five layout templates: saas-launch, ai-agent, dev-tool, community-curated and minimalist. Each one writes a valid product document you can edit.
npx @nextlevelbuilder/cli template dev-tool --out product.json2. Validate and preview
validate checks the document against the same schema the directory uses and prints its canonical SHA-256 hash. preview renders the listing in your terminal.
npx @nextlevelbuilder/cli validate product.json
npx @nextlevelbuilder/cli preview product.json3. Submit for review
npx @nextlevelbuilder/cli submit product.json --api-key $NLB_API_KEYNote
What happens next
Your revision runs through automated checks, then a person reviews it. Approval is always a named human decision, and the approved revision is exactly what gets published.
Or let your agent do it
The MCP server exposes the directory to Claude Code, Cursor, Codex and any other MCP client. Run it locally over stdio, or connect to the remote endpoint at https://mcp.nextlevelbuilder.io/mcp, which signs you in with OAuth.
{
"mcpServers": {
"nlb-directory": {
"command": "npx",
"args": ["-y", "@nextlevelbuilder/mcp"]
}
}
}| Tool | What it does |
|---|---|
list_templates | Lists the layout templates |
validate_listing | Validates a product document before submitting |
upload_media | Uploads a logo or screenshot |
submit_product | Submits a revision to the review queue |
get_leaderboard | Reads the current rankings |
get_product_markdown | Returns a listing as Markdown |
FAQ
Do I need an API key?
To submit, yes: create one from your account and pass it with --api-key or the NLB_API_KEY variable. Browsing published listings does not need one.
Where is the source?
The CLI, MCP server and shared contracts live in nlb-directory-toolkits under the MIT license.