# Connect an agent with Harbor MCP

Connect an external AI client to one project and discover its supported tools.

Reviewed: 2026-10-04
Page: https://harbor.gg/docs/agents/mcp/

## Get project access

Open [Settings → MCP](https://dashboard.harbor.gg/web-hub/settings/mcp). MCP is enabled by default on new hubs. Create a key with the access you need and store it securely; treat it as a credential. Use the endpoint and client instructions shown on that page. Production uses `https://api.harbor.gg/mcp`, with `Authorization: Bearer YOUR_MCP_KEY`. Never include a real key in a prompt, committed file, or public URL.

## Discover capabilities at runtime

Harbor supports JSON-RPC over HTTP. Start with `initialize`, then use `tools/list` to get the actual tool names, argument schemas, and availability for your key. Use `resources/list` and read `harbor://docs` for this handbook and `harbor://guide` for the operational domain model. Call `get_project_summary` to confirm the connected project.

Do not rely on a fixed tool count from older docs. Read-only keys expose a different catalog from mutation-enabled keys. `navigate_to`, `undo_last_action`, and `ask_user` are dashboard-only and are excluded from MCP.

## Understand write access

A mutation-enabled key needs an attribution account. MCP writes execute directly once authorized by the key; they do not show the dashboard’s approval cards. Have the human review the intended change before destructive operations, message sends, or publication. Use the returned schemas and real IDs, then read back affected data to verify the result.

Harbor can be operated headlessly through the tools exposed by MCP. This does not mean every dashboard capability has a tool. Discover the available catalog and report any missing operation instead of inventing a tool or calling private dashboard endpoints.