PRD Generator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_prd_from_readmeC | Generate a PRD from a README file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusing it with another. The purpose is clear and unambiguous.
The sole tool name follows a clear verb_noun pattern in snake_case. Internal consistency is perfect since there is only one tool.
One tool feels thin for a server labeled 'PRD Generator MCP Server', as it only covers a single action. However, the tool is not trivial; it performs a meaningful, focused task, so it is borderline rather than inadequate.
The domain is PRD generation, and the tool handles generating from a README, but there are no options for other input types, editing, validation, or export. This leaves notable gaps in a broader PRD workflow.