Pizza Developer

Description

Pizza Developer is where your project's plan lives. The MCP server lets your coding agent read and update that plan: your priorities, your rules, and the route each kind of request should take. Every session starts from the current state of the project instead of a blank chat, and picks up where the last one stopped. Ideas: Keep a ranked list of what you want next. Your agent plans from the top Ideas and turns each one into a Batch of ordered Works. Declined Ideas keep their reason, so agents don't suggest them again. Works: Your agent claims a Work before it edits anything. When it's done, it replaces the plan with what it actually did. If a session ends early, it leaves a handoff note for the next one. Workflows: Build the route for each kind of request, such as a bug fix or a big feature, in a visual editor. Each step comes with its own instructions and documents to read. Agents can't skip steps, and each run records where it failed and how many retries it took. Instructions: Write your rules as named documents and attach them to Workflow steps, so your agent reads the right ones at the right time. Earlier versions are kept and can be restored. Dictionary: List your product's terms and their meanings, so agents use your words instead of inventing their own. Features: List your product's features, from large areas down to single features, each with a short description. Agents use them to find where a change belongs and keep them up to date. Mark a feature hands-off and agents won't rename, move, or change it or anything under it. Deliveries: Group finished Batches into versions with a summary written for people, and share them on a Public Delivery Page with presentations and an RSS feed. For a software project, it works as a changelog. Pizza Developer never reads or changes your code. Your code stays in your repository.

Community Metrics

Categories

• mcp

Tags

• mcp
• smithery

Capabilities

• Remote MCP server

Information