Vaspera Pm MCP server

Read from the package source without running it. The installed server may list more.

• analyze_git_freshness

  Analyze documentation freshness and code-doc synchronization using git history. This tool examines git commit history to: 1. **Detect stale documentation** - Identify docs that haven't been updated in a long time 2. **Find code-doc desync** - Detect when code has changed but related docs haven't 3. **Predict drift risk** - Score files by likelihood of future drift based on patterns 4. **Surface un

• dependency_audit

  Audit project dependencies for security, updates, and health. Analyzes package.json, requirements.txt, go.mod, or similar and provides: - Security vulnerability assessment - Outdated package identification - License compliance check - Bundle size impact analysis - Maintenance health scores - Upgrade recommendations with breaking change warnings Best for: Pre-release dependency review and security

• detect_contradictions

  Scan docs/code for conflicting requirements. Returns evidence graph without resolving conflicts. Takes documentation, code, and other sources and identifies: - **Direct contradictions**: Explicitly opposing statements - **Implied contradictions**: Logically incompatible claims - **Temporal contradictions**: Newer claims that supersede older ones without removal Produces: - Contradiction report wit

• detect_regressions

  Proactively check for accidentally removed requirements. Compares the current backlog against a baseline version to find missing items. Flags critical and high-priority items that may have been unintentionally removed. Use Cases: - Pre-sync validation before pushing to ADO/Jira - Sprint planning review - Compliance audits - PRD drift detection Best for: Preventing accidental scope reduction and en

• estimate_migration

  Estimate the effort required for a code migration or major upgrade. Analyzes current code and target state to provide: - Effort estimation (story points, days) - Risk assessment - Breaking changes analysis - Migration path recommendations - Rollback strategy Supports: Framework upgrades, language migrations, architecture changes, dependency updates. Best for: Sprint planning for major technical in

• explain_codebase

  Analyze code and generate comprehensive documentation for product managers. Takes source code and produces PM-friendly documentation: - Architecture overview - Feature inventory - Data flow explanations - User-facing functionality mapping - Technical debt assessment - Business logic documentation Best for: Onboarding PMs to existing codebases or creating technical context.

• explode_backlog

  Break down high-level features or epics into detailed, actionable user stories. Takes a feature description and generates: - User stories with acceptance criteria - Story point estimates - Priority recommendations - Dependencies between stories - Frontend component stories (when includeFrontend: true) Best for: Converting feature ideas into sprint-ready backlog items.

• export_requirements

  Consolidate requirements from VasperaPM outputs into a single source of truth. Scans existing documentation (validation reports, PRDs, handoffs, specs) and produces: - Unified requirements list with IDs - Implementation status for each requirement - Evidence locations (file:line references) - ADO/JIRA-ready format for import Best for: Creating a single requirements document before sprint planning

• generate_api_docs

  Generate API documentation from source code. Analyzes API routes and generates: - OpenAPI 3.1 specification - Endpoint summaries - Request/response schemas - Authentication requirements - Example payloads Supports REST APIs in TypeScript/JavaScript, Python, Go, and more. Best for: Creating or updating API documentation from code.

• generate_architecture

  Generate a technical architecture document from product requirements. Takes a PRD or feature description and creates: - System architecture diagram (in Mermaid) - Component breakdown - Data models and schemas - API design recommendations - Technology stack suggestions - Scalability considerations Supports two modes: 1. **File mode** (recommended): Provide repoPath to auto-discover database schemas

• generate_changelog

  Generate changelogs and release notes from VasperaPM document history. Supports multiple output types: - **changelog**: Detailed diff between two versions showing added/removed/modified items - **release_notes**: Stakeholder-friendly release notes - **full_history**: Complete changelog across all versions - **scope_trend**: Track scope changes over time (scope creep detection) - **audit_summary**:

• generate_complete_backlog

  Generate a comprehensive, engineering-quality project backlog using sequential category-based AI calls. **Architecture:** Makes focused AI calls per category (one document at a time) for reliability and accuracy, then merges results with cross-referencing. **Categories generated:** - \u{1F3AF} Features - From PRD/requirements - \u{1F50C} API - From API documentation - \u{1F3D7}\uFE0F Infrastructur

• generate_deployment_runbook

  Generate a comprehensive deployment runbook for production readiness. Takes a codebase or PRD and creates: - Environment configuration guide (dev/staging/prod) - CI/CD pipeline setup (GitHub Actions, Azure Pipelines, GitLab CI) - Container orchestration guide (Docker, Kubernetes) - Monitoring and alerting setup - Rollback procedures - Health check endpoints - Secret management Supports auto-discov

• generate_sprint_report

  Generate sprint-focused report showing scope changes over a time period. Includes: - Scope comparison (start vs end) - Risk indicators (scope creep, estimate inflation, regressions) - Added/removed/modified items - Category breakdown - Recommendations Best for: Sprint reviews, stakeholder updates, planning meetings.

• generate_test_specs

  Generate comprehensive test specifications from requirements or code. Takes PRD, user stories, or source code and produces: - Test plan overview - Unit test specifications - Integration test scenarios - E2E test cases - Edge case coverage - Test data requirements - Accessibility testing checklist Best for: Ensuring comprehensive test coverage before or during development.

• get_audit_trail

  Query the audit log for compliance and debugging. Provides full traceability of all VasperaPM document changes including: - Event timeline (creates, updates, deletes, syncs) - Document changes and diff summaries - Git context (branch, commit) - Token usage tracking - Filtering by date, document type, event type Best for: Compliance audits, debugging, understanding document history.

• get_canonical_backlog

  Fetch the VALIDATED, canonical specs for this repo from VasperaPM \u2014 the approved source of truth to build against. Returns the epic\u2192story\u2192task tree of specs a human has validated, with acceptance criteria and dependencies, and (by default) each spec's latest delivery/drift status \u2014 so you get the ledger (what's approved + what shipped + what drifted), not just a snapshot. Use t

• handoff_packagewrite action

  Create a complete developer handoff package from PM artifacts. Takes PRD, designs, and specs to generate: - Implementation guide - Acceptance criteria checklist - Edge cases and error handling - Testing requirements - Definition of Done Best for: Preparing work for engineering sprint planning.

• import_verify_spec

  Verify your code against a spec produced by another tool (Amazon Kiro, GitHub Spec Kit, or a generic spec.md). Import the spec, and get a report of which requirements the code actually implements (implemented / partial / missing / contradicted) with a coverage score. One-way and read-only: it verifies the imported spec against the code and never writes back to Kiro / Spec Kit. Best for: trusting t

• infer_prd_from_code

  Analyze code and generate a Product Requirements Document (PRD). Takes code snippets, file structures, or repository descriptions and infers: - Product overview and purpose - Feature list with descriptions - User personas and use cases - Technical requirements - Non-functional requirements Best for: Documenting existing products or understanding inherited codebases.

• reverse_engineer_frontend

  Analyze frontend code to generate structured development stories. Takes React/Vue/Next.js component code and produces: - Component inventory with props and types - State management patterns - User flow documentation - API integration points - Frontend stories matching explode_backlog format Best for: Documenting existing frontend, onboarding, gap analysis.

• reverse_engineer_user_flows

  Analyze code to extract and document user flows and journeys. Takes source code (routes, components, handlers) and produces: - User journey maps - Flow diagrams (Mermaid) - Screen/state transitions - API call sequences - Error handling paths - Edge case flows Best for: Documenting existing features or understanding inherited codebases.

• review_prd

  Review and critique a Product Requirements Document. Analyzes a PRD against best practices and provides: - Completeness assessment - Clarity and ambiguity analysis - Gap identification - Risk assessment - Improvement suggestions - Readiness score Best for: Quality assurance before engineering handoff.

• run_benchmarkwrite action

  Run VasperaBench evaluation on the verification system. VasperaBench is a standardized dataset for evaluating doc-code drift detection. This tool runs the internal VasperaPM verification system against the benchmark and reports accuracy metrics. Metrics produced: - **F1 Score**: Primary ranking metric (harmonic mean of precision and recall) - **Accuracy**: Overall correct predictions - **Precision

• run_pipelinewrite action

  Execute a VasperaPM pipeline to automatically generate documentation and backlog items. Available pipelines: - **docs-first**: Start with PRD \u2192 Architecture \u2192 Tests \u2192 Backlog \u2192 Export - **code-first**: Analyze code \u2192 Infer PRD \u2192 User Flows \u2192 Tech Debt - **full**: Complete analysis combining both pipelines - **custom**: Define your own pipeline steps The pipeline

• suggest_refactors

  Analyze code and suggest refactoring opportunities for product planning. Takes source code and identifies: - Technical debt items - Refactoring opportunities - Architecture improvements - Performance optimizations - Maintainability issues Produces PM-friendly documentation for sprint planning. Best for: Technical debt prioritization and architecture evolution planning.

• sync_to_tracker

  Format requirements and user stories for import into project management tools. Takes requirements or a PRD and generates properly formatted items for: - Jira (Epics, Stories, Tasks, Subtasks) - Azure DevOps (Epics, Features, User Stories, Tasks) - Linear (Projects, Issues, Sub-issues) - GitHub Issues (Issues with labels and milestones) Output formats: - **JSON**: Structured data for API-based impo

• synthesize_master_prd

  Synthesize multiple input documents into a unified Master PRD. Takes multiple sources (meeting notes, emails, specs, designs) and creates: - Unified product vision - Consolidated requirements - Prioritized feature list - Clear success metrics - Risk assessment Best for: Creating a single source of truth from scattered documentation.

• synthesize_requirements

  Extract and synthesize requirements from various input sources with CONFLICT DETECTION. Takes meeting notes, emails, slack threads, user feedback, or any unstructured input and produces: - Functional requirements (what the system must do) - Non-functional requirements (performance, security, scalability) - User stories in standard format - Acceptance criteria for each requirement - Requirement dep

• tasks_cancelwrite action

  Cancel a pending or running task

• tasks_list

  List all tasks with optional filtering

• tasks_result

  Get the full result of a completed task

• tasks_status

  Get the status of a running or completed task

• track_estimates

  Analyze estimate changes over time across backlog versions. Provides: - Historical trend of total story points - Version-by-version changes - Top estimate inflators (items with largest increases) - Category-level breakdown - Inflation alerts and recommendations Best for: Sprint planning, identifying estimate drift, tracking scope creep.

• validate_implementation

  Validate that code implementation matches requirements. Compares source code against PRD/requirements and produces: - Requirements coverage report with specific file:line references - Gap analysis with actionable recommendations - AST-based verification for accurate code location - Acceptance criteria verification Supports two modes: 1. **File mode** (recommended): Provide repoPath to read actual

• verify_agents_md

  Verify an AGENTS.md / CLAUDE.md against the actual code, and emit a corrected, verified section. AGENTS.md is what coding agents read to understand your project. When it drifts from the code, every agent acts on stale instructions. This tool: - scores an existing AGENTS.md's accuracy (each claim marked verified / stale / unsupported) with a machine-readable accuracy percent, and - emits a correcte

• verify_docs_code

  Verify documentation against code implementation to detect drift. Uses a multi-agent system to: 1. Discover all documentation and code files 2. Extract requirements from docs and features from code 3. Cross-validate to detect drift, undocumented features, and unimplemented requirements 4. Optionally debate findings for higher accuracy Returns a comprehensive verification report with: - Summary sta

• Code scan7 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Vaspera Pm: common questions

Is Vaspera Pm MCP server safe?

With care: it is graded C, so read the findings first (55/100). Read the Vaspera Pm safety report

How do I install Vaspera Pm?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Vaspera Pm need an API key?

Yes. The registry entry asks for ANTHROPIC_API_KEY, VASPERA_API_KEY.

Is Vaspera Pm maintained?

The latest release is v2.15.0.

What can I use instead of Vaspera Pm?

Servers from other publishers that do the same job: SvGrid MCP server, Mdma MCP server and AI Context MCP server. Compare all Vaspera Pm alternatives.