project-hub

Project Hub MCP Server provides a comprehensive suite for managing local projects, tracking changes, handling local Git-like operations, and integrating with GitHub. It includes features for creating and managing projects, scanning source files with customizable exclusions, recording and linking changes to commits, and maintaining rich notes. The local Git functionality supports creating commits and branches, capturing snapshots with metadata, restoring to past states, and cloning from commits or branches. The GitHub integration extends repository management, commit tracking with file content, branch operations, pull requests, and multi-account support. This MCP server exposes a set of tools under the Project Management, Change Management, Local Git, File Snapshot, Note Management, and Repository Management modules, enabling automated workflows and centralized project governance.

To use the server, first ensure the MCP server is running with the project-hub entry. Then access the tools via the API or CLI endpoints described in your implementation, using names like create_project, find_project, init_local_repository, create_local_commit, get_file_snapshots, create_note, and create_repository. Each tool accepts parameters as described in the README, allowing you to manage projects, changes, local history, notes, file content, and GitHub repositories from a single interface.

Prerequisites:

• Node.js (v14+ recommended) installed on the host machine
• Access to a network to communicate with GitHub if using GitHub features
• Optional: Docker if you prefer containerized deployment

Step-by-step installation:

1. Clone the repository or obtain the MCP server package for Project Hub.

2. Install dependencies (if using a Node.js project):

   npm install

3. Configure environment variables as needed (see additional_notes for common options). Create an .env file if required by your setup.

4. Run the server:

   node server.js

5. Verify the server is listening on the expected port and accessible via your client API.

6. (Optional) If you prefer Docker, build and run the container using your Dockerfile or image as per your Docker setup instructions.

Notes and tips:

• If you enable GitHub integration, configure authentication tokens and repository access in your environment or configuration files. Ensure tokens have appropriate scopes for repository management, commits, branches, and pull requests.
• The project search supports case-insensitive and partial matching. You can refine results with filters like type and has_repo when listing projects.
• For file scanning, tailor excludePatterns to keep generated or transient files out of scans.
• When restoring to a local commit or branch, verify the working directory state and any untracked changes to avoid conflicts.
• Enable multi-account support for GitHub by providing credentials or per-account tokens and configuration in the Repository Management module.
• When using snapshots, consider fetching metadata separately if you need to minimize payload size or protect file contents; use get_file_snapshots_metadata to retrieve metadata without file content.
• Review the default branch and repository settings in your GitHub integration (rename, delete, merge operations have implications for CI/CD and collaborators).