MCP Sources

MCP sources connect Harbor to remote MCP servers. Once registered, agents call the server's tools through the standard CLI — no local MCP client setup needed.

Registering an MCP source

The full MCP registration flow with endpoint probing and OAuth is on the dedicated MCP page (/mcp in the dashboard). There's also an MCP Sources tab on the Plugins page for quick registration.

MCP page flow

Dashboard → /mcp → Add MCP Source:

• Slug — short name, becomes part of the CLI command (harbor p.mcp.<slug>)
• Display name — human-readable label
• Endpoint — the server URL (HTTPS required). Harbor auto-probes the endpoint and shows:
  • Connection status and discovered tools count
  • Whether the server requires OAuth (and whether it supports dynamic client registration)
  • Auto-fills slug and display name from the server's reported name
• Transport — HTTP, SSE, or stdio
• Auth mode — None, Bearer, API key, or OAuth
  • OAuth fields (when selected): authorization URL, token URL, client ID/secret, scope

After saving, the source appears with its status (connected / disconnected / error / requires_oauth) and tool count. A refresh button re-probes the endpoint.

Calling MCP tools

harbor plugins tools mcp.linear       # see available tools
harbor p.mcp.linear create_issue --title "Bug"
harbor p.mcp.slack post_message --channel general --text "Done"

Managing sources

Each registered source shows:

• Connection status with a refresh button
• List of discovered tools
• Agent access section (same lease model as other plugins — grant/revoke per agent)

Sources can be refreshed, have OAuth reconnected/disconnected, or be deleted.