add_validation_rule
Add a custom validation rule
LABSCO SUMMARY
The templates and the rules are data, which is what makes the second document match the first.
A prompt can write a product requirements document once. What separates this is that both halves are persisted and editable: templates are created, revised through update, and moved between machines as JSON, while validation rules are pattern-based and extensible, with list_all_rules showing yours next to the defaults. That turns "how we write PRDs" into something enforced rather than remembered. health_check covering the database and the providers together is a candid acknowledgement that generation depends on an external service that can be down.
What it is
A PRD server built around three managed collections — templates, validation rules and AI provider configuration — with generation, rendering and validation running over them.
What you get
- generate_prd, producing a document from a named template given the product name, description, target audience, core features and constraints
- render_template, the same placeholder substitution without the generation step
- validate_prd, checking a document against best-practice rules, with the rule set listable first
- Custom validation rules added, updated and deleted by pattern, and list_all_rules showing defaults and custom rules together
- Template management: create, list, get by ID or name, update, soft-delete, and export or import the whole set as a JSON file
- AI provider handling: the available providers with their status, the stored configuration overrides, and updates to providerId, apiKey, baseUrl and model
- Operational tooling: usage metrics per operation, a health check covering the database and the providers, and recent log entries read from disk
Requirements
For the generation tools, a configured AI provider — list_ai_providers reports which are available and update_provider_config takes the providerId, apiKey, baseUrl and model. The template and validation-rule tools work without one.
Setup effort
One command — npx -y prd-creator-mcp
USE CASES
01
Getting a first draft PRD out of a product brief
Pick a template from the stored set, generate the document from product name, description, audience, core features and constraints, then run it through validation before anyone reads it.
02
Turning your team's review checklist into something enforced
Add the checks your reviewers keep repeating as named rules with a pattern, list them beside the defaults to see the whole rule set, and edit one when it turns out to be too strict.
03
Moving a house style onto a teammate's machine
Export the whole template set to a JSON file, import it on the other side, and confirm what landed. Deletion is a soft delete, so a template dropped by mistake is not gone from the store.
04
Filling a template without calling a model at all
Render the template with the same inputs generation takes and get placeholder substitution only — useful when the document is boilerplate, or when no provider is configured.
05
Working out why generation stopped working
Check the database and providers in one call, see which providers report themselves available, read the recent log lines from disk, and correct the stored apiKey, baseUrl or model for the provider that is failing.
21 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_template
Create a new PRD template
delete_template
Soft-delete a PRD template by ID
delete_validation_rule
Delete a custom validation rule
export_templates
Export all PRD templates to a JSON file
generate_prd
Generate a Product Requirements Document from a template
get_logs
Retrieve recent log entries from disk
get_provider_config
Retrieve stored provider configuration overrides
get_template
Get a PRD template by ID or name
health_check
Perform system health check (DB + AI providers)
import_templates
Import PRD templates from a JSON file
list_ai_providers
List all available AI providers and their availability status
list_all_rules
List all validation rules (default + custom)
list_templates
List all non-deleted PRD templates
list_validation_rules
List all available validation rules
render_template
Render a PRD template with placeholder substitution
stats
Retrieve usage metrics for operations
update_provider_config
Update stored provider configuration override
update_template
Update an existing PRD template
update_validation_rule
Update a custom validation rule
validate_prd
Validate a PRD against best practices
BEFORE YOU INSTALL
What to know first
Tools you get
21 tools when we connected. add_validation_rule, update_validation_rule, delete_validation_rule and list_all_rules are available but missing from the documentation. Without a provider key, generate_prd falls back to the template provider.
Requires
- npx on PATH
- Node.js v16 or later
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 21 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y prd-creator-mcpMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"prd-creator": {
"command": "npx",
"args": [
"-y",
"prd-creator-mcp"
]
}
}
}Roo Code
ROO CODE · JSON
{
"mcpServers": {
"prd-creator-mcp": {
"command": "npx",
"args": [
"-y",
"prd-creator-mcp"
]
}
}
}
