PM-Skills MCP

Open-source MCP server exposing 40 best-practice product management skills plus workflows and lifecycle tools, instantly accessible to any AI via Model Context Protocol.

Report a Bug · Request a Feature · Ask a Question

Want to customize skills or use slash commands? This server is powered by pm-skills, the open-source skill library you can fork and modify. Browse the full catalog, interactive showcase, and setup guides at product-on-purpose.github.io/pm-skills.

[!IMPORTANT] Maintenance Mode (effective 2026-05-04)

Active development on pm-skills-mcp is paused pending demonstrated demand. The current release (v2.9.2) remains fully functional and exposes the full pm-skills catalog of 40 PM skills, 11 workflows, and 8 utility tools (59 tools total) via the Model Context Protocol. Security patches and critical bug fixes will continue to be addressed; new skill parity with the upstream pm-skills library is on hold.

For new users: the file-based install path documented in the main pm-skills repository is under active maintenance and is the recommended path going forward.

To register interest in resumed development: open a GitHub Discussion.

About • Getting Started • Usage • Status • Contributing • Community

Quick Start (NPM Global Install)

npm install -g pm-skills-mcp

The Big Idea

PM-Skills MCP is an MCP server that transforms PM-Skills, a collection of 40 best-practice product management skills, into programmatically accessible tools, resources, and prompts for any AI assistant that speaks the Model Context Protocol.

PM-Skills MCP is built on pm-skills, an open-source collection of 40 PM skills organized by the Triple Diamond framework. While pm-skills offers file-based access with slash commands and AGENTS.md discovery, pm-skills-mcp wraps those same skills in an MCP server for programmatic access. The pm-skills library now includes lifecycle tools (Create, Validate, Iterate) and a documentation site with an interactive showcase.

Not sure which to use? See the Comparison section below, or the MCP Setup Guide on the docs site.

One connection. 40 skills. Any MCP client.

Why MCP?

The Model Context Protocol is an open standard that lets AI assistants connect to external tools and data sources. Instead of manually copying skill files or uploading ZIP archives, PM-Skills MCP gives your AI direct, programmatic access to the entire PM skill library.

The Transformation

Key Features

• 59 MCP Tools - 40 PM skills + 11 workflows + 8 utility tools
• MCP Resources - Skill instructions, templates, and examples via URI, with optional persona resources when enabled
• 3 MCP Prompts - Guided conversation starters for common workflows
• 11 Workflows - Pre-built multi-skill workflows for common scenarios
• 81 Automated Tests - Comprehensive test coverage with Vitest
• Zero Configuration - Works out of the box with embedded skills
• Universal Compatibility - Claude Desktop, Cursor, Continue, and any MCP client
• Customizable - Override with your own skill modifications
• Lightweight - Minimal dependencies, fast startup
• Security Scanning - CodeQL analysis on every push

Built with...

• Model Context Protocol - Open standard for AI tool connectivity
• PM-Skills - The 40 PM skills this server exposes (docs site)
• TypeScript - Type-safe implementation
• Vitest - Fast, modern testing framework

Works for...

PM-Skills MCP works with any client that supports the Model Context Protocol. Here's a quick overview:

Platform Compatibility

See the Integration Guide for detailed setup instructions for each platform.

Comparison: pm-skills-mcp (this repo) vs. pm-skills

PM-Skills is available in two complementary forms:

Use pm-skills-mcp (this repo) when:

• You want instant setup with npx pm-skills-mcp
• You're using Claude Desktop, Cursor, or any MCP client
• You want programmatic tool access without managing files
• You prefer consistent interfaces across different AI clients

Use pm-skills (file-based) when:

• You prefer slash commands in Claude Code (/prd, /hypothesis)
• You want to browse, read, and customize skill files directly
• You're using GitHub Copilot, OpenCode, or Windsurf without reliable MCP support
• You want to fork and heavily customize skills for your team

Using Both Together: Fork pm-skills to customize skills, then point pm-skills-mcp to your fork:

{
  "mcpServers": {
    "pm-skills": {
      "command": "npx",
      "args": ["pm-skills-mcp"],
      "env": {
        "PM_SKILLS_PATH": "/path/to/my/forked/pm-skills/skills"
      }
    }
  }
}

(back to top)

Getting Started

This section covers quick installation. For a comprehensive walkthrough including core concepts, your first tool invocation, workflows, and troubleshooting, see the Getting Started Guide.

NPM Global Install

npm install -g pm-skills-mcp

Run directly:

pm-skills-mcp

From Source

git clone https://github.com/product-on-purpose/pm-skills-mcp.git
cd pm-skills-mcp
npm install
npm run build
npm start

Quick Start by Platform

{
  "mcpServers": {
    "pm-skills": {
      "command": "npx",
      "args": ["pm-skills-mcp"]
    }
  }
}

{
  "mcpServers": {
    "pm-skills": {
      "command": "npx",
      "args": ["pm-skills-mcp"]
    }
  }
}

{
  "pm-skills": {
    "command": "npx",
    "args": ["pm-skills-mcp"]
  }
}

{
  "mcpServers": {
    "pm-skills": {
      "command": "npx",
      "args": ["pm-skills-mcp"]
    }
  }
}

{
  "mcpServers": {
    "pm-skills": {
      "command": "npx",
      "args": ["pm-skills-mcp"]
    }
  }
}

Configuration

Environment Variables

Custom Skills Path

Override embedded skills with your customized versions:

{
  "mcpServers": {
    "pm-skills": {
      "command": "npx",
      "args": ["pm-skills-mcp"],
      "env": {
        "PM_SKILLS_PATH": "/path/to/my/custom/skills"
      }
    }
  }
}

Using Custom Skills from a pm-skills Fork

If you've forked pm-skills to customize skills:

1. Clone your fork locally
2. Make changes to skills in skills/{phase-skill}/ (e.g., skills/deliver-prd/)
3. Point pm-skills-mcp to your fork:

{
  "mcpServers": {
    "pm-skills": {
      "command": "npx",
      "args": ["pm-skills-mcp"],
      "env": {
        "PM_SKILLS_PATH": "/path/to/my-pm-skills-fork/skills"
      }
    }
  }
}

See the pm-skills authoring guide for skill modification guidelines.

(back to top)

Usage

How It Works

┌─────────────────────────────────────────────────────────────┐
│                    Your AI Assistant                        │
│              (Claude, Cursor, Continue, etc.)               │
└──────────────────────────┬──────────────────────────────────┘
                           │ MCP Protocol
                           ▼
┌─────────────────────────────────────────────────────────────┐
│                    pm-skills-mcp Server                     │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│   ┌─────────────┐   ┌─────────────┐   ┌─────────────┐       │
│   │   59 Tools  │   │  Resources  │   │  3 Prompts  │       │
│   │             │   │             │   │             │       │
│   │ • 40 skills │   │ • templates │   │ • kickoff   │       │
│   │ • 11 flows  │   │ • examples  │   │ • lean      │       │
│   │ • 8 utils   │   │ • skills    │   │ • quick-prd │       │
│   │             │   │             │   │             │       │
│   └─────────────┘   └─────────────┘   └─────────────┘       │
│                                                             │
│   ┌─────────────────────────────────────────────────────┐   │
│   │              Embedded PM-Skills Library             │   │
│   │     40 skills × (SKILL.md + TEMPLATE + EXAMPLE)     │   │
│   └─────────────────────────────────────────────────────┘   │
│                                                             │
└─────────────────────────────────────────────────────────────┘

1. You ask your AI to create a PRD, hypothesis, or any PM artifact
2. AI invokes the appropriate pm_* tool via MCP
3. Server returns skill instructions, template, and optionally an example
4. AI generates a professional-quality artifact following the skill framework

Tools

PM-Skills MCP wraps each skill from pm-skills as an MCP tool. The 40 skill tools (like pm_prd, pm_hypothesis, pm_acceptance_criteria, pm_pm_skill_builder) generate PM artifacts, while 11 workflow tools and 8 utility tools help you orchestrate and validate skill usage. See the Comparison section for when to use MCP tools vs file-based slash commands.

Every skill tool accepts these parameters:

Example invocations:

# Basic usage
Use pm_prd with topic "user authentication for mobile app"

# With context
Use pm_hypothesis with topic "checkout abandonment" and context "We see 40%
cart abandonment. Hypothesis: users abandon due to required account creation."

# Request concise output with example
Use pm_user_stories with topic "dark mode" format "concise" includeExample true

The Skills

🔍 Discover Phase - Find the right problem

📋 Define Phase - Frame the problem

💡 Develop Phase - Explore solutions

🚀 Deliver Phase - Ship it

📊 Measure Phase - Validate with data

🔄 Iterate Phase - Learn and improve

🧭 Foundation - Cross-cutting capability

🔗 Workflows - Multi-skill workflows

🛠️ Utility Tools

(back to top)

MCP Resources

Access skill content directly via MCP resources:

pm-skills://skills/{skill}      → Full skill instructions
pm-skills://templates/{skill}   → Template only
pm-skills://examples/{skill}    → Worked example

Examples:

pm-skills://skills/deliver-prd
pm-skills://templates/define-hypothesis
pm-skills://examples/measure-experiment-design

Note: Phase information is available in resource metadata.

(back to top)

Prompts

MCP prompts provide guided conversation starters for common workflows. Use prompts/get with the prompt name and a topic to begin.

Usage example:

prompts/get name="feature-kickoff" arguments={"topic": "dark mode support"}

(back to top)

Guides

Comprehensive documentation for setup, customization, and understanding pm-skills-mcp.

(back to top)

Project Status

Development Status

Maintenance mode as of 2026-05-04. Active feature development is paused pending demonstrated demand. The project will continue to receive security patches and critical bug fixes; new skill parity with the upstream pm-skills library is on hold pending a sustained signal of multi-team adoption.

Resumption criteria. A sustained signal of demand via GitHub Discussion engagement, install-volume growth, or direct contact from teams adopting the server in production workflows.

Recommended path for new users. The file-based install via the main pm-skills repository remains under active maintenance and is the supported path going forward. The main repository carries current parity with the latest pm-skills releases (40 skills as of v2.13.0).

To register interest: open a GitHub Discussion.

Releases

All releases are available on the GitHub Releases page.

Install the latest version:

npm install -g pm-skills-mcp

Install a pinned release:

npm install -g pm-skills-mcp@2.7.0

From v2.4.0 onward, pm-skills-mcp directly tracks pm-skills release versions. Pinned source compatibility metadata is declared in pm-skills-source.json for each release.

Latest: docs/releases/Release_v2.7.0.md | Previous release details | Full changelog

Project Structure

See docs/reference/project-structure.md for detailed descriptions.

pm-skills-mcp/
├── src/                      # TypeScript source code
│   ├── index.ts              # Entry point
│   ├── server.ts             # MCP server implementation
│   ├── config.ts             # Configuration management
│   ├── cache.ts              # Skill caching layer
│   ├── skills/               # Skill loader and parser
│   ├── tools/                # MCP tool handlers (59 tools)
│   ├── resources/            # MCP resource handlers (skills/templates/examples + optional personas)
│   ├── prompts/              # MCP prompt definitions (3 prompts)
│   ├── workflows/            # Workflow definitions
│   └── types/                # TypeScript type definitions
├── skills/                   # Embedded PM skills (flat, copied from pm-skills v2.x)
│   ├── deliver-prd/          # Example: phase-prefixed skill directories
│   ├── define-hypothesis/    # Each skill has SKILL.md + references/
│   ├── discover-interview-synthesis/
│   └── ...                   # 40 skills total
├── docs/                     # Documentation
│   ├── getting-started.md    # Complete setup and first-use guide
│   ├── integration-guide.md  # Client-specific configuration
│   ├── customization.md      # Using custom skills with MCP
│   ├── migration-guide.md    # Moving between file-based and MCP
│   ├── architecture.md       # Technical internals for contributors
│   ├── releases/             # Shipped release notes
│   └── reference/            # Reference documentation
│       ├── project-structure.md
│       └── repository-governance.md
├── tests/                    # Vitest test suites (81 tests)
├── scripts/                  # Build and utility scripts
├── dist/                     # Compiled JavaScript output
├── .github/                  # CI/CD workflows
│   └── workflows/            # ci.yml, publish.yml, codeql.yml
├── pm-skills-source.json     # Pinned pm-skills repo/ref/version metadata
├── AGENTS.md                 # Agent discovery file
├── CONTRIBUTING.md           # Contribution guidelines
├── SECURITY.md               # Security policy
└── CHANGELOG.md              # Version history

Previous Release Details

Changelog

See CHANGELOG.md for full version history.

Roadmap

See the open issues for planned features.

• Core MCP server with all 40 PM skills
• Workflow tools (11 workflows)
• MCP resources for direct skill access
• MCP prompts for guided workflows
• Automated npm publishing
• Skill versioning and compatibility tracking
• Additional workflows
• Custom skill contribution support

(back to top)

Development

Testing

The project uses Vitest for testing with 81 tests across multiple test files.

# Run all tests
npm test

# Watch mode for development
npm run test:watch

# Generate coverage report
npm run test:coverage

Test coverage includes:

• Skill loader and parser
• Tool handler and response formatting
• Workflow execution
• Prompt registration
• Output validation
• Server initialization

Code Quality

# Lint with ESLint
npm run lint

# Auto-fix lint issues
npm run lint:fix

# Format with Prettier
npm run format

# Check formatting
npm run format:check

# Type check
npx tsc --noEmit

CI/CD

The project uses GitHub Actions for continuous integration and deployment:

CI Workflow (.github/workflows/ci.yml)

• Triggers on push/PR to main
• Tests on Node.js 18, 20, and 22
• Runs lint, format check, type check, and tests
• Clones pm-skills at the pinned ref from pm-skills-source.json and embeds skills for testing

Publish Workflow (.github/workflows/publish.yml)

• Triggers on GitHub release creation
• Auto-publishes to npm with provenance
• Uses npm automation token for authentication
• Embeds skills from the same pinned pm-skills ref declared in pm-skills-source.json

CodeQL Workflow (.github/workflows/codeql.yml)

• Security scanning for JavaScript/TypeScript
• Runs on push to main and weekly schedule

(back to top)

Security

We take security seriously. This project includes:

• CodeQL Analysis - Automated security scanning on every push
• Dependabot - Automated dependency updates for npm and GitHub Actions
• Vulnerability Reporting - See SECURITY.md for our security policy

To report a vulnerability, please email security concerns privately rather than opening a public issue. See SECURITY.md for details.

(back to top)

Contributing

Contributions are what make the open-source community such an amazing place to learn, inspire, and create. Any contributions you make will benefit everybody else and are greatly appreciated.

How to Contribute

Quick contribution steps:

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
3. Commit your Changes using Conventional Commits (git commit -m 'feat: add amazing feature')
4. Push to the Branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

Please read our CONTRIBUTING.md for detailed guidelines.

Reporting Bugs

Please try to create bug reports that are:

• Reproducible - Include steps to reproduce the problem
• Specific - Include as much detail as possible (version, environment, etc.)
• Unique - Do not duplicate existing opened issues
• Scoped - One bug per report

(back to top)

About

Author

Howdy, I'm Jonathan Prisant, a product leader/manager/nerd in the church technology space who gets unreasonably excited about understanding + solving problems, serving humans, designing elegant systems, and getting stuff done. I enjoy optimizing and scaling workflows more than is probably healthy... NOT because I'm particularly fond of "business process definition", but because I think in systems and value the outcomes of increased "effectiveness and efficiency" (i.e. doing less of the boring work and more of the work I actually enjoy).

I am a follower of Jesus Christ, grateful husband to my beloved, proud (and exhausted) dad of 4 humans of various sizes and ages, D&D geek, 3d printing enthusiast, formerly-consistent strength trainer, smart home enthusiast, insatiable learner, compulsive tech-experimenter, writer-of-words that aggregate into sentences and paragraphs, and a bunch of other stuff too. I have too many projects going on across too many domains and need better self control, but hopefully you find this open-source repo helpful and useful.

If PM-Skills has helped you ship better products, consider giving the repo a star and sharing it with your team.

License

Distributed under the Apache License 2.0. See LICENSE for more information.

This means you can:

• Use PM-Skills MCP commercially
• Modify and distribute
• Use privately
• Include in proprietary software

The only requirements are attribution and including the license notice.

Security

We take security seriously. This project includes:

• CodeQL Analysis - Automated security scanning on every push
• Dependabot - Automated dependency updates for npm and GitHub Actions
• Vulnerability Reporting - See SECURITY.md for our security policy

To report a vulnerability, please email security concerns privately rather than opening a public issue.

Acknowledgments

• PM-Skills - The skill library that powers this MCP server. All 25 PM skills, templates, and examples come from pm-skills.
• Model Context Protocol - The protocol that makes this possible
• Anthropic - For creating MCP and Claude

(back to top)

Community

Have ideas for making PM-Skills MCP even better? Here are some ways to contribute and connect:

Feature Ideas

• Open a feature request to suggest improvements
• Join the Discussions to brainstorm with the community

Spread the Word

• Give the repo a star if you find it useful
• Share PM-Skills MCP with your team
• Write about how you use PM-Skills MCP in your workflow

Feedback

• Found something confusing? Open an issue
• Want to chat? Start a discussion

Built with purpose by Product on Purpose
_{Bringing professional PM skills to every AI assistant}

(back to top)