project-planner-mcp
v1.0.0
Published
AI-driven project planning and execution orchestrator with GitHub integration
Maintainers
Readme
Project Planner MCP Server
AI-driven project planning and execution orchestrator with GitHub integration.
Installation
Claude Code (Recommended)
Add to your Claude Code MCP settings:
{
"mcpServers": {
"project-planner": {
"command": "npx",
"args": ["-y", "project-planner-mcp"],
"env": {
"GITHUB_TOKEN": "your-github-token"
}
}
}
}Manual Installation
npm install -g project-planner-mcpThen add to your MCP settings:
{
"mcpServers": {
"project-planner": {
"command": "project-planner-mcp",
"env": {
"GITHUB_TOKEN": "your-github-token"
}
}
}
}GitHub Token
Get a GitHub Personal Access Token at https://github.com/settings/tokens
Required scopes:
repo(all)admin:org(read:org) - optional, for organization projects
Overview
This MCP server provides intelligent project planning capabilities with GitHub integration, combining:
- Interactive Discovery - AI-driven Q&A that challenges assumptions and finds gaps
- Requirements Analysis - Deep analysis for completeness, conflicts, and feasibility
- Project Planning - Automated generation of comprehensive project plans
- GitHub Integration - Full orchestration of issues, projects, milestones, and PRs
- Progress Tracking - Real-time sync between local state and GitHub
- Intelligence Engine - Cross-project learning and pattern recognition
Architecture
project-planner-mcp/
├── package.json
├── tsconfig.json
├── src/
│ ├── index.ts # MCP server entry point
│ ├── types/
│ │ ├── tools.ts # Tool parameter/return types
│ │ ├── resources.ts # Resource types
│ │ ├── prompts.ts # Prompt types
│ │ └── common.ts # Shared types
│ ├── tools/
│ │ ├── planning/ # Planning tools
│ │ ├── github/ # GitHub integration
│ │ └── intelligence/ # Intelligence tools
│ ├── resources/ # Resource handlers
│ ├── prompts/ # Prompt handlers
│ ├── services/ # Business logic
│ └── database/ # SQLite databaseTools (11 total)
Planning Tools (4)
- conductDiscovery - Interactive AI-driven Q&A with assumption checking
- analyzeRequirements - Gap finding, conflict detection, feasibility analysis
- generateProjectPlan - Create PROJECT_PLAN.md and REQUIREMENTS.md files
- critiquePlan - Review existing plans for issues and improvements
GitHub Integration Tools (5)
- setupGitHubProject - Create issues, milestones, project board from plan
- syncWithGitHub - Bidirectional sync between .agent-state.json and GitHub
- trackProgress - Query GitHub for progress metrics and status
- updateSessionStatus - Update session status in GitHub issue
- findNextSession - Find next session based on dependencies
Intelligence Tools (2)
- reviewArchitecture - Review for patterns, anti-patterns, security, scalability
- estimateEffort - Data-driven estimates from historical project data
Resources (4 categories)
- Projects (
project://*) - Access to all tracked projects - Templates (
template://*) - Project templates (blog, ecommerce, saas, etc.) - Patterns (
pattern://*) - Best practices database - Metrics (
metrics://*) - Historical metrics and learnings
Prompts (3)
- discovery-questions - Generate intelligent discovery questions
- architecture-review - Comprehensive architecture review
- estimate-effort - Effort estimation with historical context
Integration with Existing System
This MCP server complements the existing .claude/ system:
MCP Handles:
- Interactive planning and discovery
- GitHub orchestration and tracking
- Cross-project intelligence
- Requirements analysis and critique
.claude/ Handles:
- Templates and generated plans (version controlled)
- Execution agents (backend-builder, frontend-builder, etc.)
- Session state tracking (.agent-state.json)
- TDD workflow execution
Workflow Example
// 1. Discovery (MCP)
const discovery = await mcp.conductDiscovery({
projectType: "ecommerce"
});
// 2. Generate Plan (MCP writes to .claude/)
await mcp.generateProjectPlan({
discoverySummary: discovery.summary,
outputPath: "project-plans/my-store"
});
// 3. Setup GitHub (MCP + GitHub MCP)
await mcp.setupGitHubProject({
owner: "user",
repo: "my-store",
planPath: "project-plans/my-store/PROJECT_PLAN.md"
});
// 4. Execute Sessions (.claude/ agents)
/execute-session my-store 1
// Agents auto-update GitHub via MCP
// 5. Track Progress (MCP)
const progress = await mcp.trackProgress({
owner: "user",
repo: "my-store"
});Database Schema
SQLite database tracks:
- Projects (name, type, complexity, GitHub info)
- Sessions (status, metrics, GitHub issue/PR mapping)
- Patterns (best practices with usage/success rates)
- Metrics (time, coverage, velocity per project)
- Learnings (cross-project insights)
Configuration
User config in ~/.project-planner-config.json:
- Database path
- GitHub token
- Default settings
- Intelligence options
Type Safety
Full TypeScript with strict mode:
- All tool parameters/returns typed
- All resources typed
- All prompts typed
- Zod schemas for runtime validation
Files in This Specification
README.md- This overviewpackage.json- NPM package configurationtsconfig.json- TypeScript configurationtypes/common.ts- Shared type definitionstypes/tools.ts- Tool parameter/return typestypes/resources.ts- Resource typestypes/prompts.ts- Prompt typesindex.ts- MCP server implementationdatabase-schema.ts- Database schema and initializationconfig-template.json- Configuration file template
Implementation Status
Status: v1.0.0 Released
- 11 MCP tools implemented
- 4 resource handlers
- 3 prompt templates
- 593+ tests passing
- Full TypeScript with strict mode
See CHANGELOG.md for details.
License
MIT - See LICENSE for details.
