| 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).
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 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.
/project-hub:setup
The skill works through these steps:
python3, python, py -3 and, on Windows, known install locations).~/.project-hub/.~/.project-hub/venv if it is missing.requirements.txt and removes an old fastmcp package if present.config.example.yaml to ~/.project-hub/config.yaml if no configuration exists yet. An existing file is never overwritten.db_path points to a cloud-sync folder or a network path.~/.project-hub/knowledge/. Existing files stay untouched.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.
/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.
claude plugin update project-hub, then restart Claude Code./project-hub:setup again. The skill always syncs the dependencies and leaves existing data and configuration untouched./project-hub:knowledge sync. The skill first shows what is new or changed and only overwrites after you confirm.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.