Project Hub MCP Server

Project Hub MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for managing software projects, providing tools for project tracking, note-taking, and GitHub integration.

What you get

An MCP server providing comprehensive project management, local Git functionality, and GitHub integration capabilities. This server enables managing local projects, tracking changes, creating local commits, and synchronizing with GitHub repositories.

What the assistant can call

Once Project Hub is connected, these are the calls the assistant has available:

• create_project — Create a new project with local and remote repository management. - name: Project name - path: Local project path - type: Project type -
• find_project — Find a project by name (flexible, case-insensitive, partial match). Returns detailed project information including changes and notes. - name
• list_projects — List all projects with optional filtering. - type: Filter by project type (optional) - has_repo: Filter by repository presence (optional) -
• update_project_details — Update details of an existing project. - projectId: Project ID - name: New project name (optional) - path: New project path (optional) -
• delete_project — The delete_project tool exposed by this server
• scan_project_files — Scan a project directory for source files and update the project record. - projectId: Project ID - excludePatterns: Regex patterns to exclude
• projectdb_location — The projectdb_location tool exposed by this server
• record_change — Record a change in a project. - projectId: Project ID - type: Change type - description: Change description - files: List of file
• get_pending_changes — Get pending changes for a project. - projectId: Project ID
• clear_committed_changes — Clear committed changes for a project. - projectId: Project ID
• init_local_repository — Initialize a local Git repository for a project. - projectId: Project ID
• create_local_commit — Create a local commit from pending changes. - projectId: Project ID - message: Commit message - authorName: Author name (optional) -

Configuration and credentials

You will need 4 environment variables: DEFAULT_PRIVATE, DEFAULT_OWNER, GITHUB_TOKEN, GIT_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Project Hub's toolset — create_project, find_project, list_projects and 11 more — is a fair guide to whether it matches your workflow. It is maintained by peterparker57; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Project Hub's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Project Hub.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the project hub mcp server does with a few real requests.