Skip to main content
Glama
Njengah

PRD Generator MCP Server

by Njengah

PRD Generator - Claude Desktop Extension

PRD Generator Screenshot

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:

  1. Reads your project's README file

  2. Extracts key information from the content

  3. Generates a structured Product Requirements Document

  4. 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

  1. Download the latest prd-generator.dxt file from the releases

  2. Open Claude Desktop

  3. Go to Settings > Extensions

  4. Drag the .dxt file into the window or click "Upload"

  5. Click "Install"

  6. 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.md

The 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.js

Building the Extension

# Package into .dxt file
npx @anthropic-ai/dxt pack

Testing

  1. Ensure your server runs without errors

  2. Test with a sample README file

  3. 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

  1. Fork the repository

  2. Create a feature branch: git checkout -b feature/amazing-feature

  3. Commit your changes: git commit -m 'Add amazing feature'

  4. Push to the branch: git push origin feature/amazing-feature

  5. Open 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

  1. Install Claude Desktop (latest version)

  2. Download the .dxt file

  3. Install via Settings > Extensions

  4. Test with: "Generate a PRD from my README at /path/to/readme.md"

Available Tools

1 tool
generate_prd_from_readmeC

Generate a PRD from a README file

ParametersJSON Schema
NameRequiredDescriptionDefault
readme_pathYesPath to README file

TDQS

C2.9/5.0
Behavior2/5

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.

Conciseness4/5

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.

Completeness2/5

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.

Parameters3/5

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.

Purpose4/5

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.

Usage Guidelines2/5

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. 1 tool update
    • First observedgenerate_prd_from_readme

TDQS

B3.1/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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

ActivityInactive
ResponsivenessSyncing

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

Related MCP Servers

Latest Blog Posts

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