Skip to main content
Glama

Fork Parity MCP

by moikas-code

🔄 Fork Parity MCP

Track and manage fork parity with upstream repositories using Model Context Protocol (MCP)

A powerful MCP server that helps you stay in sync with upstream repositories by tracking changes, analyzing commits, and managing integration status. Perfect for maintaining forks while keeping track of upstream developments.

✨ Features

  • 🔍 Smart Change Detection - Automatically detect new upstream commits
  • 📊 Parity Status Tracking - Track which commits have been reviewed, integrated, or skipped
  • 🎯 Commit Analysis - Deep dive into specific commits to understand their impact
  • 📋 Adaptation Planning - Generate actionable plans for integrating upstream changes
  • 🌿 Branch Comparison - Compare your fork with upstream branches
  • ⚙️ Flexible Configuration - Support for custom remote names and branches
  • 🚀 CLI Integration - Works seamlessly with Claude and other MCP clients

🚀 Quick Start

Installation

npm install -g @moikas/parity-mcp

Basic Setup

  1. Configure your Git remotes:
# Add upstream remote (if not already added) git remote add upstream https://github.com/original/repository.git # Verify remotes git remote -v
  1. Add to your MCP configuration:
{ "mcpServers": { "fork-parity": { "command": "fork-parity-mcp", "env": { "REPO_PATH": "/path/to/your/fork" } } } }
  1. Start tracking:
# Fetch latest upstream changes git fetch upstream # You're ready to go! 🎉

📖 Usage

Once configured, you can interact with the MCP server through natural language:

🔍 Check for New Changes

"Check for new upstream changes in the last week" "Show me commits since last month"

📊 Analyze Specific Commits

"Analyze commit abc123 for compatibility" "What files were changed in commit def456?"

🎯 Compare Branches

"Compare our authentication module with upstream" "Show differences in src/ directory"

📋 Plan Integration

"Create an adaptation plan for the latest 5 commits" "What commits need review?"

⚙️ Manage Status

"Mark commit abc123 as integrated" "Show current parity status"

🛠️ Available Tools

ToolDescription
check_upstream_changesFind new commits in upstream repository
analyze_commitAnalyze specific commit for compatibility
compare_branchesCompare fork with upstream branch
get_parity_statusGet current tracking status
update_parity_statusUpdate commit integration status
create_adaptation_planGenerate integration roadmap
fetch_upstreamFetch latest upstream changes
show_configDisplay current configuration
setup_upstreamHelp configure upstream remote

⚙️ Configuration

Environment Variables

VariableDefaultDescription
UPSTREAM_REMOTE_NAMEupstreamName of upstream remote
UPSTREAM_BRANCHmainUpstream branch to track
REPO_PATHprocess.cwd()Path to Git repository

Advanced Configuration

{ "mcpServers": { "fork-parity": { "command": "fork-parity-mcp", "env": { "UPSTREAM_REMOTE_NAME": "origin-upstream", "UPSTREAM_BRANCH": "develop", "REPO_PATH": "/home/user/my-fork" } } } }

Multiple Projects

Track multiple forks simultaneously:

{ "mcpServers": { "project-a-parity": { "command": "fork-parity-mcp", "env": { "REPO_PATH": "/home/user/project-a" } }, "project-b-parity": { "command": "fork-parity-mcp", "env": { "REPO_PATH": "/home/user/project-b", "UPSTREAM_BRANCH": "development" } } } }

📁 Status Tracking

The server creates a .parity-status.json file to track:

{ "commits": { "abc123": { "status": "integrated", "notes": "Applied with modifications for our auth system", "timestamp": "2024-01-15T10:30:00Z" }, "def456": { "status": "skipped", "notes": "Not applicable to our fork", "timestamp": "2024-01-15T11:00:00Z" } }, "lastUpdated": "2024-01-15T11:00:00Z" }

Status Types

  • integrated - Successfully merged/applied
  • 🔍 reviewed - Analyzed but not yet integrated
  • ⏭️ skipped - Not applicable to your fork
  • ⚠️ conflict - Requires manual resolution

🔧 Development

Prerequisites

  • Node.js 18+
  • Git repository with upstream remote

Local Development

# Clone the repository git clone https://github.com/moikas/parity-mcp.git cd parity-mcp # Install dependencies npm install # Run locally node fork-parity-server.js

Testing

# Run tests npm test # Lint code npm run lint # Check package npm pack --dry-run

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your 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

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

  • Built with Model Context Protocol (MCP)
  • Inspired by the need to maintain fork parity in open source projects
  • Thanks to the MCP community for the excellent SDK

🏠 Homepage📖 Documentation🐛 Report Bug✨ Request Feature

Made with ❤️ for the open source community

Related MCP Servers

  • A
    security
    A
    license
    A
    quality
    A specialized MCP server for in-depth analysis of git repositories, offering tools for branch overview, time period analysis, file changes, and merge recommendations.
    Last updated -
    4
    1
    JavaScript
    Apache 2.0
  • A
    security
    F
    license
    A
    quality
    MCP server for managing Git operations on local repositories, allowing users to list repositories, get and create tags, list commits, push tags, and refresh repositories through a standardized interface.
    Last updated -
    6
    3
    Python
  • A
    security
    A
    license
    A
    quality
    A MCP server that provides access to GitHub trending repositories and developers data through a simple API interface.
    Last updated -
    2
    13
    Python
    MIT License
    • Apple
  • A
    security
    F
    license
    A
    quality
    An MCP server that provides seamless interaction with Azure DevOps Git repositories, enabling users to manage repositories, branches, pull requests, and pipelines through natural language.
    Last updated -
    8
    2
    3
    TypeScript

View all related MCP servers

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/moikas-code/fork-parity-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server