Install
$ agentstack add mcp-joshuashunk-harbor Open-source listing, not yet scanned by AgentStack. Follow the source repository for install instructions.
Security review
⚠ Flagged1 finding(s); flagged for manual review. · v0.1.0 How review works →
- • Prompt-injection patterns
- • Secret / credential exfiltration
- • Dangerous shell & filesystem operations
- • Untrusted network calls
- • Known-malicious package signatures
- high Pipes remote content directly into a shell (remote code execution).
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Harbor
Universal MCP Hub — discover, install, run, and sync MCP servers across every host.
Website · Docs · Download · Discussions · Issues
What is Harbor?
Harbor is a desktop app and CLI that manages MCP (Model Context Protocol) servers from a single place. Instead of editing JSON and TOML configs by hand across every host, you dock servers once and Harbor syncs them everywhere.
- One config, every host — sync to Claude Code, Codex, VS Code, and Cursor simultaneously
- Marketplace — search and install MCP servers from the MCP Registry without leaving the app
- Secret vault — store API keys in your OS keychain, reference them as
vault:SECRET_NAME - HTTP/SSE gateway — expose your MCP servers over HTTP for remote access and tool discovery
- Desktop + CLI — full GUI built with Tauri, or use the CLI for automation and scripting
- Safe merges — Harbor never overwrites your host configs, it merges its servers in alongside yours
Quick Start
Install
curl -fsSL https://harbormcp.ai/install.sh | sh
On macOS this installs the desktop app and CLI together. On Linux it installs the CLI.
> You can also download the desktop app directly for macOS, Windows, and Linux.
Your First Server
# Link a host
harbor port link claude
# Dock a server — it syncs automatically to linked hosts
harbor dock --name memory --command npx --args @modelcontextprotocol/server-memory
# Check your fleet
harbor fleet
CLI Reference
Harbor uses a nautical theme — every command has a standard alias if you prefer.
| Command | Alias | Description | |---------|-------|-------------| | harbor dock | add | Dock a new MCP server into the harbor | | harbor undock | remove | Undock a server and cast it off | | harbor fleet | list | Review your fleet of docked servers | | harbor launch | start | Launch a server out to sea | | harbor manifest | status | Read the harbor manifest | | harbor port | host | Manage port connections (link/unlink hosts) | | harbor sync | signal | Sync server configs to linked hosts | | harbor lighthouse | gateway | Light the lighthouse (HTTP/SSE gateway) | | harbor scout | search | Scout the seas for MCP servers | | harbor chest | vault | Open the treasure chest (secret vault) | | harbor cargo | filter | Inspect or filter tool access per server | | harbor crew | team | Manage team fleet sync across your crew | | harbor scuttle | uninstall | Scuttle the ship (uninstall Harbor) | | harbor update | — | Update Harbor to the latest version |
Team Fleet Sync (harbor crew)
Share MCP server configs across your team via a git-backed fleet repository. Secrets stay local — only vault:KEY_NAME references are committed.
# Set up a shared fleet (one person)
harbor crew init --git git@github.com:your-org/fleet.git
harbor crew push github linear # share servers with the team
# Teammates join
harbor crew join git@github.com:your-org/fleet.git
# Day-to-day workflow
harbor crew pull # pull upstream changes
harbor crew status # see drift at a glance
harbor crew provision # stow any missing vault secrets
| Subcommand | Description | |------------|-------------| | crew init [--git ] | Initialize a local fleet repo, optionally linking a remote | | crew join | Clone a team fleet and auto-pull | | crew push [] [-m ] | Share servers with the team | | crew pull [--dry-run] | Merge upstream changes into your local config | | crew status | Show git sync status and per-server drift | | crew provision [--dry-run] | Prompt for missing vault secrets |
Supported Hosts
| Host | Config File | Sync Key | |------|------------|----------| | Claude Code | ~/.claude.json | mcpServers | | Codex | ~/.codex/config.toml | mcp_servers | | VS Code | .vscode/mcp.json | servers | | Cursor | ~/.cursor/mcp.json | mcpServers |
Configuration
Harbor stores its config at ~/.harbor/config.toml. You can edit it directly or manage everything through the app and CLI.
Vault References
Store secrets in your OS keychain and reference them in server environment variables:
# Store a secret
harbor chest set OPENAI_API_KEY sk-...
# Reference it in a server
harbor dock --name my-server --command npx --args my-mcp-server \
--env OPENAI_API_KEY=vault:OPENAI_API_KEY
Vault references are resolved at runtime — your secrets never end up in plain-text config files.
Gateway (Lighthouse)
The lighthouse is Harbor's gateway server. The desktop app starts it automatically on launch. It handles tool filtering, vault resolution, hot reload, and exposes endpoints for tool discovery (GET /tools), JSON-RPC (POST /mcp), and server-sent events (GET /sse).
For CLI users, start the gateway manually:
harbor lighthouse --port 3100
Architecture
Harbor is a Rust workspace with three crates:
harbor-core Core library — config, connectors, gateway, vault, marketplace
harbor-cli CLI binary — clap-based command interface
harbor-desktop Desktop app — Tauri v2 shell wrapping the React frontend
Tech stack: Rust, Tauri v2, React 19, TypeScript, Tailwind CSS, Axum
Building from Source
Prerequisites
Desktop App
git clone https://github.com/JoshuaShunk/Harbor.git
cd Harbor
# Install frontend dependencies
cd ui && npm ci && npm run build && cd ..
# Run in development
cd crates/harbor-desktop && cargo tauri dev
# Or build for production
cd crates/harbor-desktop && cargo tauri build
CLI Only
cargo build --release -p harbor-cli
Examples
See the [examples/](examples/) directory for sample configurations:
- [
basic-server.toml](examples/basic-server.toml) — Minimal server config - [
multi-host.toml](examples/multi-host.toml) — Server synced to multiple hosts - [
fleet-team.toml](examples/fleet-team.toml) — Team fleet setup
Contributing
Contributions are welcome! Please read the [Contributing Guide](CONTRIBUTING.md) before submitting a pull request.
License
[MIT](LICENSE)
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: JoshuaShunk
- Source: JoshuaShunk/Harbor
- License: MIT
- Homepage: https://harbormcp.ai
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.