HarborHarbor
DocumentationGuidesPlugins
Get Started

Connect Gemini CLI

Point Gemini CLI at Harbor's MCP server.

Gemini CLI speaks Model Context Protocol (MCP) over streamable HTTP. Pointing it at Harbor takes one config block.

You need to be logged in to Harbor first — see Sign up & install hrbr.

Open the config file

~/.gemini/settings.json

If the file doesn't exist, create it.

Paste the Harbor block

{
  "mcpServers": {
    "harbor": { "url": "https://mcp.tryharbor.ai/mcp" }
  }
}

If you already have other MCP servers configured, add the harbor entry next to them under the same mcpServers object.

Restart Gemini CLI

The first time you invoke a Harbor tool from inside Gemini CLI, your browser opens for OAuth 2.1 + PKCE. Consent, return to the editor, and the agent now has inspect + exec against your workspace.

Try it

Ask your agent something only Harbor can answer:

"List my five most recent Linear issues."

Gemini CLI calls Harbor's inspect tool to discover the right plugin, then exec to run the search. Watch the run land in Traces.

Tool budget

Gemini CLI sees only two tools from Harbor — inspect and exec. It doesn't matter how many plugins your workspace has (5 or 500), the visible tool budget stays the same. See For Agents → Connecting for the pattern.

Where to go next

Install your first plugin →

Your first exec →

Connect Codex

Point Codex CLI at Harbor's MCP server.

Install your first plugin

Connect a service, inspect readiness, and run your first tool with real CLI commands.

On this page

Open the config filePaste the Harbor blockRestart Gemini CLITry itTool budgetWhere to go next