PRD Generator MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PRD Generator MCP Servergenerate a PRD from the README at /projects/api-service/README.md"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PRD Generator - Claude Desktop Extension

A simple Claude Desktop Extension (DXT) that generates Product Requirements Documents (PRDs) from README files with a single click.
Features
One-click installation - No complex setup or configuration files
Automatic PRD generation from README files
File system access - Read README files from any path
Time-saving documentation - Generate structured PRDs in seconds
Cross-platform support - Works on Windows, Mac, and Linux
Related MCP server: gitSERVER README Manager
What This Extension Does
This extension provides a simple tool that:
Reads your project's README file
Extracts key information from the content
Generates a structured Product Requirements Document
Saves you time on documentation tasks
Prerequisites
Claude Desktop (latest version with DXT support)
Node.js (bundled with Claude Desktop)
DXT Toolchain:
npm install -g @anthropic-ai/dxt
Installation
Option 1: Install Pre-built Extension
Download the latest
prd-generator.dxtfile from the releasesOpen Claude Desktop
Go to Settings > Extensions
Drag the
.dxtfile into the window or click "Upload"Click "Install"
Done!
Option 2: Build from Source
# Clone the repository
git clone https://github.com/yourusername/prd-generator-dxt.git
cd prd-generator-dxt
# Install dependencies
npm install
# Test the server
npm start
# Package the extension
npx @anthropic-ai/dxt packš ļø Usage
After installation, you can use the extension in Claude Desktop:
Generate a PRD from my README at /path/to/your/readme.mdThe extension will:
Read your README file
Extract the first 5 lines as the project description
Generate a structured PRD with sections for:
Project Overview
Description
Key Features
Technical Requirements
Generation timestamp
Project Structure
prd-generator/
āāā server/
ā āāā index.js # Main MCP server code
āāā manifest.json # Extension configuration
āāā package.json # Node.js dependencies
āāā package-lock.json # Dependency lock file
āāā README.md # This fileš§ Development
Running Locally
# Start the MCP server
npm start
# Or run directly
node server/index.jsBuilding the Extension
# Package into .dxt file
npx @anthropic-ai/dxt packTesting
Ensure your server runs without errors
Test with a sample README file
Verify the generated PRD format
Generated PRD Format
The extension generates PRDs with the following structure:
# Product Requirements Document
## Project Overview
Based on: [README file path]
## Description
[First 5 lines from README]
## Key Features
- Feature extraction from README
- Automated PRD generation
- Time-saving documentation
## Technical Requirements
- Node.js runtime
- File system access
- README file parsing
Generated on: [ISO timestamp]Contributing
Fork the repository
Create a feature branch:
git checkout -b feature/amazing-featureCommit your changes:
git commit -m 'Add amazing feature'Push to the branch:
git push origin feature/amazing-featureOpen a Pull Request
Todo / Future Enhancements
Support for multiple README formats (rst, txt, etc.)
Customizable PRD templates
Integration with project management tools
Advanced content extraction and analysis
Support for configuration files (package.json, etc.)
š Known Issues
Path handling may vary between operating systems
Large README files might cause performance issues
Currently only supports UTF-8 encoded files
š Resources
š License
This project is licensed under the MIT License - see the LICENSE file for details.
Note: This is a basic implementation demonstrating Claude Desktop Extensions. For production use, consider adding error handling, input validation, and more sophisticated README parsing.
š Quick Start
Install Claude Desktop (latest version)
Download the
.dxtfileInstall via Settings > Extensions
Test with: "Generate a PRD from my README at /path/to/readme.md"
Available Tools
1 toolgenerate_prd_from_readmeC
Generate a PRD from a README file
| Name | Required | Description | Default |
|---|---|---|---|
| readme_path | Yes | Path to README file |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must disclose behavioral traits. It does not mention any side effects, error conditions, or output characteristics, leaving the agent uninformed about the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise, using a single sentence. It is not verbose, but could be slightly more informative without sacrificing brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of output schema and annotations, the description is insufficient. It does not explain what the generated PRD contains, any constraints, or how the README is processed, leaving significant gaps for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, with the parameter 'readme_path' described. The tool description does not add extra meaning beyond the schema, so a baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (Generate) and the resource (PRD from a README file). It is specific enough to understand the tool's function, though it lacks details about the PRD format.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. Since there are no sibling tools, the need is lower, but the description offers no context for appropriate use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- First observed
generate_prd_from_readme
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate_prd_from_readme' has a clearly defined and distinct purpose.
With only one tool, naming consistency is inherently perfect. The tool name 'generate_prd_from_readme' follows a clear verb_noun pattern and there are no other tools to create inconsistency.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. For a PRD generator, one tool feels thin and may not cover related operations like editing, validating, or managing PRDs.
The server is severely incomplete for PRD generation. It only offers generation from README files, with no tools for creating, updating, deleting, or managing PRDs from other sources, nor for handling PRD lifecycle operations like review or approval.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Turn PRDs and product ideas into structured specs so coding agents build your intent, not theirs.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Extract PDFs to Markdown, RAG chunks and cited tables; publish tracked Doc Links with read stats.
Markdown workspace for AI agents: read, write, organize, and share markdown documents.
Related MCP Servers
- -licenseBqualityNot gradedmaintenanceAutomates the creation of standardized documentation by extracting information from source files and applying templates, with integration capabilities for GitHub, Google Drive, and Perplexity AI.33-
- FlicenseNot gradedqualityDmaintenanceEnables automated README file management for development projects through MCP tools for content creation and summarization, resources for direct file access, and prompts for AI-powered documentation analysis.-
- FlicenseBqualityDmaintenanceEnables LLMs to automatically analyze project structures, detect technologies, and generate comprehensive, professional README documentation files with proper formatting, badges, and sections.41-
- AlicenseNot gradedqualityNot gradedmaintenanceAutomatically generates Chinese README documentation and mind maps for project folders, enabling intelligent documentation management and project structure visualization.-
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Njengah/prd-dxt'
If you have feedback or need assistance with the MCP directory API, please join our Discord server