Project Hub - Installation
Requirements, installing Project Hub via marketplace or git clone, first-time setup with /project-hub:setup, updates and removal of the plugin.
Project Hub - Installation
Requirements
| Component | Requirement |
|---|---|
| Claude Code | with plugin support |
| Python | 3.11 or newer |
| Operating system | Linux, macOS or Windows (native, no WSL needed) |
| Network | only during setup, to download the Python packages |
No API key is needed. The Python packages are listed in the plugin's requirements.txt: mcp[cli] (version 2.x), jinja2, pyyaml and markitdown (with the extras for PDF, DOCX, XLSX and XLS).
Installation routes
Marketplace
claude plugin marketplace add markus-michalski/project-hub
claude plugin install project-hub@project-hub
Updates then run via claude plugin update project-hub.
Git clone
git clone https://github.com/markus-michalski/project-hub ~/.claude/plugins/project-hub
Then enable the plugin in ~/.claude/settings.json:
{
"enabledPlugins": {
"project-hub@project-hub": true
}
}
This route also needs the first-time setup. The MCP server starts through the Python in
~/.project-hub/venv, which only/project-hub:setupcreates.
First-time setup
/project-hub:setup
The skill works through these steps:
- It looks for a working Python interpreter (
python3,python,py -3and, on Windows, known install locations). - It creates
~/.project-hub/. - It creates the virtual environment
~/.project-hub/venvif it is missing. - It syncs the dependencies from
requirements.txtand removes an oldfastmcppackage if present. - It copies
config.example.yamlto~/.project-hub/config.yamlif no configuration exists yet. An existing file is never overwritten. - It warns if
db_pathpoints to a cloud-sync folder or a network path. - It asks for which project types the knowledge document templates should be copied to
~/.project-hub/knowledge/. Existing files stay untouched. - It initializes the database.
Restart Claude Code afterwards so the MCP server is loaded.
Windows: if
pythonorpython3fails with exit code 49 and no output, that is the Microsoft Store placeholder. The skill then falls back topy -3automatically.
Verifying the installation
/project-hub:session-start checks that the venv, config.yaml and the Python dependencies exist and points you to /project-hub:setup if anything is missing. /project-hub:help lists all skills.
Updates
- Marketplace:
claude plugin update project-hub, then restart Claude Code. - After an update you can run
/project-hub:setupagain. The skill always syncs the dependencies and leaves existing data and configuration untouched. - Compare updated knowledge document templates with
/project-hub:knowledge sync. The skill first shows what is new or changed and only overwrites after you confirm. - The database schema is extended automatically when the MCP server starts. The server creates missing tables and columns itself.
Removal
The repository does not describe its own uninstall procedure. Your data lives outside the plugin directory and therefore survives removal of the plugin:
| Path | Content |
|---|---|
~/.project-hub/ |
Configuration, database, virtual environment, knowledge documents, custom project types, reports, exports |
docs_root (see Configuration) |
Project folders with note files and attachments |
To remove everything, delete these folders manually. This cannot be undone, because the database holds all projects, contacts and notes.