Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.harbormcp.ai/llms.txt

Use this file to discover all available pages before exploring further.

Harbor supports syncing your MCP server fleet to multiple AI development tools simultaneously.

Supported Hosts

HostConfig FileConfig Key
Claude Code~/.claude.jsonmcpServers
Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonmcpServers
Codex~/.codex/config.tomlmcp_servers
VS Code.vscode/mcp.jsonservers
Cursor~/.cursor/mcp.jsonmcpServers

Linking Hosts

Before Harbor can sync to a host, you must link it:
harbor port link claude
harbor port link claude-desktop
harbor port link vscode
Or use the Ports page in the desktop app and click Link next to each host.

Automatic Syncing

Harbor automatically syncs your fleet to all linked hosts whenever you:
  • Dock or undock a server
  • Toggle a server on/off
  • Link or unlink a host
You can also force a manual sync with harbor signal or the Signal All button in the desktop app.

How Syncing Works

Each host stores MCP server configuration in its own format. Harbor handles the translation:
1

Read

Harbor reads the host’s existing config file.
2

Merge

Your enabled servers are merged into the config. Servers you’ve configured directly in the host are left untouched.
3

Resolve

Any vault: references in environment variables are resolved to actual values from your OS keychain.
4

Write

The updated config is written back to the host’s config file.

Per-Host Control

You can enable or disable individual servers for specific hosts. A server might be enabled for Claude Code but disabled for Cursor:
[servers.github]
url = "https://api.githubcopilot.com/mcp/"
enabled = true

[servers.github.hosts]
claude = true
claude-desktop = true
codex = true
vscode = false
cursor = false

Safe Merges

Harbor never overwrites your host configs. It identifies which servers it manages and only modifies those entries, leaving your manually-configured servers intact.