Connect Hover to Claude.

What this does

Hover runs a connector that Claude talks to over the Model Context Protocol (MCP), the open standard Claude uses to reach external tools. Once you add it, you can ask Claude about your fleet in plain language and it reads the answers straight from your Hover organization: deployments, flights, recordings, detections, telemetry, and assets. It is read-only. The connector can look, not change anything.

Before you start

• A Hover account.
• A way to run Claude: Claude Code, a claude.ai Pro or Max plan, or Claude Desktop.

You do not need an API key. You connect by entering one URL and signing in to Hover through your browser.

Connect Hover

Every surface uses the same connector URL:

https://mcp.hoverfeed.com/mcp

You enter it once, Claude opens a browser sign-in to Hover, you approve read-only access, and you are connected. There is no key or secret to paste.

Claude Code

Run this in your terminal:

claude mcp add --transport http hover https://mcp.hoverfeed.com/mcp

The first time Claude uses a Hover tool, it opens a browser to sign in and approve. Add --scope user to make Hover available in every project rather than only the current one.

claude.ai and Claude Desktop

Claude brokers remote connectors through your Claude account, so a connector you add on claude.ai is automatically available in Claude Desktop under the same Connectors menu. Add it once on the web.

On claude.ai (Pro or Max):

1. Open Customize → Connectors, click +, then Add custom connector.
2. Enter https://mcp.hoverfeed.com/mcp. Leave Advanced settings blank; Hover registers itself automatically, so the Client ID and Secret fields there do not apply.
3. Click Add. Claude runs the sign-in: log in to Hover (or reuse an existing session), review the read-only consent, and Approve.
4. To use Hover in a chat, click + at the lower left, choose Connectors, and toggle Hover on.

On a Team or Enterprise plan, an Owner adds Hover first under Organization settings → Connectors → Add → Custom, then each member connects it from Customize → Connectors with the Connect button next to Hover.

For Anthropic's full walkthrough, see their custom connectors guide.

Hover plugin (best-effort)

Claude Code also has a Hover plugin. It is convenient, but currently best-effort: the plugin's browser login can dead-end on a local localhost error caused by an upstream Claude Code issue.

/plugin marketplace add hoverhq/claude-plugins
/plugin install hover@hover

If the login dead-ends on a localhost error, use the claude mcp add command above instead; that path is proven. If Claude Code prompts you to paste a callback URL, pasting it can also recover the login. A fix for the plugin login is pending upstream in Claude Code.

Approve the connection

However you connect, Hover shows a consent screen before anything is shared. It grants Claude read-only access to your own organization's:

• Deployments
• Flights
• Recordings
• Detections
• Telemetry (observations)
• Assets

The screen states plainly that the connector can never modify or control anything, and that only your own organization's data is visible. Choose Approve to connect, or Deny to stop.

Ask Claude about your fleet

Once connected, ask in plain language:

• "List my Hover deployments."
• "Show the recent detections for my harbor deployment."
• "What flights ran today, and how long was each?"

Claude calls the connector, reads your organization's data, and answers in the conversation.

What Claude can see

The connector is read-only across your operational data: deployments, flights, recordings, detections, telemetry, and assets. There are no write actions, so Claude cannot arm, disarm, or change anything through it. It returns your own organization's data and nothing else.

To disconnect, remove the Hover connector in Claude: under Connectors on claude.ai or Desktop, or by removing the Hover MCP server in Claude Code.