# Hover MCP connector

The Hover connector brings capture requests, deliverables, estimates, inspections and blueprints into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, with each person signed in to Hover as themselves and every call written to an audit log.

Source: https://elaichi.ai/connectors/hover/

## Facts

| | |
| --- | --- |
| Application | Hover |
| Category | CRM |
| AI tools | 72 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Hover is connected

- Which capture requests from this week are still waiting on photos?
- List the deliverables ready for the Henderson roof job.
- Summarize the open estimates for the Oak Street addresses.

## Connect Hover in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Hover.
2. Optionally set Share with, then press Connect.
3. Supply your own Hover app, then approve. Hover needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Hover tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Hover MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Hover MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Hover MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Hover MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Hover MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Hover to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Hover tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Hover through Elaichi

### Order a capture before the sales call

Sales. Create a Hover capture request for the homeowner's address and resend the link if the photos never arrive. Check later whether the deliverable is ready before you drive out.

### Pull the estimate into the proposal

Estimating. Look up the estimate for a job and have the numbers explained in plain language, then create the order document once the homeowner signs.

### Fix a measurement before the crew goes

Production. Raise a deliverable change request when the model missed a dormer, check the upgrade price, and cancel the request if the crew lead already sorted it on site.

### Hand the inspection to the adjuster

Claims. Share the inspection workflow, pull the inspection PDF and the photos, and answer the adjuster's question without opening the job yourself.

### Start a blueprint from the capture

Design. Create a blueprint once the deliverable lands, then list the floor plan wireframes and exports the design team needs for the drawing set.

### Check the agreement before you invoice

Office. Look up the agreement for a job and list the estimates and deliverables tied to it so the invoice matches what was actually ordered.

## Elaichi vs Zapier MCP vs Composio for Hover

All three can connect Hover to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Hover tools | Allow or restrict single Hover tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Hover call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Hover to Claude?

Connect Hover in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Hover needs an OAuth application registered inside your own Hover account, so one person brings that client ID and secret to Elaichi once. After that, everyone else just signs in to Hover with their own login and never sees the secret.

### Does Hover work with ChatGPT and Cursor as well as Claude?

Yes. Once Hover is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Hover once and every client picks it up.

### What can an AI agent actually do with my Hover data?

It can create and resend capture requests, check whether a deliverable is ready, look up an estimate or agreement, raise or cancel a deliverable change request, pull inspection photos and PDFs, and start a blueprint. Short, concrete asks work best, such as which Hover capture requests from this week are still waiting on photos.

### Does connecting Hover give the AI access to every job in my account?

No. Each person signs in to Hover as themselves, so an agent only sees the capture requests, deliverables and estimates that person can already open in Hover. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what Hover already allows.

### Can my team share one Hover connection?

Yes. One person connects Hover in Elaichi and shares it with a team, and nobody else ever handles the client ID or secret. Each teammate still signs in as themselves, so every capture request or estimate they touch is logged under their own name.

### Can I stop an agent from deleting or changing things in Hover?

Yes. Restrictions in Elaichi work per action, so you can allow reading Hover estimates and deliverables while restricting deleting capture requests or raising change requests, set on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it whatever the prompt says.

### What happens to a Hover connection when someone leaves?

Offboarding that person in Elaichi ends their access to Hover through every client at once. A shared Hover connection keeps working for everyone else on the team. If you want Hover gone entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor and every other client.

### Does the Hover MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Hover is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Hover?

Yes. Both let Claude, ChatGPT or Cursor use Hover. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Hover call.

### How is Elaichi different from Composio for Hover?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Hover: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 72 Hover tools

Every tool below is callable through https://api.elaichi.ai/mcp once Hover is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Get single Hover agreement by ID** (Get). Get Agreement Details. Returns an agreement's details, including its PDF link and production lists. Required: id.
- **Create a Hover blueprint** (Create). Blueprint Upload - Build All. Use this endpoint to upload a blueprint and reconstruct all elevations on the blueprint as their own Jobs. Covers both of Hover's blueprint uploads: workflow `build_all` (Hover builds every structure it finds) or `specify_details` (send job_attributes.name[] and job_attributes.deliverable_id[] per elevation). Through the connector, reference the blueprint files (PDF, DWG, DXF) by URL in job.file_attachments_attributes[].url; uploading local files (job[files][]) isn't supported here. Needs the blueprints feature on the Hover org. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: current_user_id, job.name, job.deliverable_id, job.file_attachments_attributes, job.file_attachments_attributes[].url, workflow.
- **Get single Hover capture request link by ID** (Get). Get Capture Request Link. Get the raw HTML page for a Capture Request using this endpoint. The id is the capture request's identifier (e.g. xpod232), not its numeric id. Hover answers with a small HTML page that redirects to the capture link. Required: id. Returns the file (text/html), not JSON.
- **List all Hover capture requests** (List). List Capture Requests. Use this endpoint to list all capture requests for your organization, given a user ID. States: new, connected, complete, deleted. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: current_user_id.
- **Get single Hover capture request by ID** (Get). Show Capture Request Details. This endpoint takes in a numeric capture request ID and returns its details. The id is the numeric capture request id. Required: id.
- **Create a Hover capture request** (Create). Create a Capture Request. This endpoint initiates a Hover property capture by creating a draft job in your authenticated organization and sending an invitation (via email/SMS) to a designated user to perform the capture. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: capture_request.capturing_user_email, capture_request.capturing_user_name, capture_request.job_attributes.location_line_1.
- **Delete a Hover capture request by ID** (Delete). Delete Capture Request. Delete an existing Capture Request using this endpoint. Required: id.
- **Hover capture requests resend** (Resend). Resend Capture Request Notifications. Resend a Capture Request notification using this endpoint. Required: capture_request_id.
- **Hover capture requests lookup** (Action). Check for Existing Capture Request. Check if there is an existing Capture Request for an email using this endpoint. Required: email.
- **List all Hover deliverable change requests** (List). List Deliverable Change Requests. Retrieve a list of all deliverable change requests for a specific Model. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: current_user_id, model_id.
- **Create a Hover deliverable change request** (Create). Create Deliverable Change Request. Create a request to upgrade and pay for a Model to have an upgraded deliverable. Upgrades a model's deliverable: Capture Only (7) to Roof Only (2) or Complete (3), Roof Only (2) to Complete (3). Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: new_deliverable_id, current_user_id, model_id.
- **Hover deliverable change requests cancel** (Cancel). Delete Pending Change Order Request. Endpoint to delete a pending deliverable change request. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: current_user_id, model_id.
- **Get single Hover deliverable upgrade price by ID** (Get). Get Upgrade Price. Retrieve pricing information for upgrading an existing deliverable for a model. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: id, new_deliverable_id, current_user_id.
- **List all Hover deliverables** (List). List Available Deliverables. Use this endpoint to retrieve a list of available deliverables for an input Wallet ID. Required: wallet_id.
- **Create a Hover estimate order document** (Create). Create Order Documents PDF or CSV. Creates a new order document for an Estimate. Required: project_management_production_list_id.
- **Get single Hover estimate order document by ID** (Get). Show Order Documents PDF or CSV. Poll the status and get back the order documents. Poll until state is complete, then download pdfLink / csvLink. Required: id, project_management_production_list_id.
- **List all Hover estimates** (List). List Estimates. List Estimates on a Job by Job ID. Required: job_id.
- **Get single Hover estimate by ID** (Get). Show Estimate Details. Get the details of a specific estimate given its ID. Required: id.
- **List all Hover esx exports** (List). Get ESX Export. The endpoint returns ESX file with the filename, {job_id}_{model_id}.esx. Required: model_id. Returns the file (application/octet-stream (Xactimate ESX)), not JSON.
- **List all Hover floor plan wireframes** (List). Get Wireframe Images. Returns a model's floor plan wireframe image (wireframe_floor_plan.png). For Interior (8) models. Required: model_id. Returns the file (image/png), not JSON.
- **List all Hover fml exports** (List). Get FML Export. This endpoint returns the FML file for Interior models only. The Hover web application refers to this file as XML 2.0 when manually exporting. However, these point to the exact same file export as this endpoint. Required: model_id. Returns the file (FML (Floorplanner JSON)), not JSON.
- **Get single Hover inspection PDF by ID** (Get). Get Inspection PDF. Use this endpoint to retrieve an Inspection’s data in PDF format. Required: id. Returns the file (application/pdf), not JSON.
- **List all Hover inspection photos** (List). Get Inspection Photos. Returns an inspection's photos (file name, sort order and image URLs). Required: inspection_id.
- **Create a Hover inspection workflow share** (Create). Share Inspection Workflow. Use this endpoint to share an Inspection Workflow with an organization. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: current_user_email, recipient_org_id, inspection_workflow_id.
- **Get single Hover inspection workflow by ID** (Get). Get Inspection Workflow Details. Use this endpoint to return specific Inspection workflow details when passing in an inspection workflow ID. Required: id.
- **List all Hover inspections** (List). List Inspections. Use this endpoint to return Inspections for a given Job. Required: job_id.
- **Get single Hover inspection by ID** (Get). Get Inspection Details. Use this endpoint to return detailed Inspection information such as questions, answers, photos, and tags for a given inspection ID. Required: id.
- **List all Hover instant design images** (List). List Instant Design Images. Returns Instant Design images for a job or a lead: send job_id or lead_id.
- **Get single Hover instant design image by ID** (Get). Show Instant Design Image. Use this endpoint to return the Instant Design image of the input image ID. Required: id, job_id.
- **List all Hover instant design leads** (List). List Instant Design Leads. Use this endpoint to list all lead information submitted through the Instant Design lead form associated with the authenticated organization. Required: org_id. The connector pages through all results (25 per page, or your limit).
- **Get single Hover instant design lead by ID** (Get). Show Instant Design Lead Details. Use this endpoint to retrieve detailed information for a single Instant Design lead given the lead ID. Required: id.
- **List all Hover job shares** (List). List Job Share Links. Use this endpoint to list all Job Shares across all jobs that the input user has access to. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: current_user_id. The connector pages through all results.
- **Get single Hover job share by ID** (Get). Show Job Share Link. Use this endpoint to return the information and links for an input Job Share ID. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: id, current_user_id.
- **Create a Hover job share** (Create). Create Job Share Link with Password. Use this endpoint to create a shareable link for a Virtual Walkthrough on a job that can be password protected. Required: job_id, viewer_version.
- **Update a Hover job share by ID** (Update). Update Job Share Link. Use this endpoint to update a Job Share link. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: id, current_user_id.
- **Delete a Hover job share by ID** (Delete). Delete Job Share Link. Use this endpoint to delete a specific Job Share link. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: id, current_user_id.
- **List all Hover jobs** (List). List Jobs. This endpoint provides information on the jobs in the authenticated organization. Filter with search (3+ characters: job name, address or user), archived, example, updated_since (epoch seconds), deliverable_ids and reconstruction_states (arrays); sort with sort_by / sort_order. The connector pages through all results (25 per page, or your limit, max 100).
- **Get single Hover job by ID** (Get). Show Job Details. Returns everything about one job: address, customer, capture session and its models. Includes each model (structure) with its state, deliverable, artifact links (measurements, CAD exports) and images; check a model's state is complete before fetching its artifacts. Required: id.
- **Create a Hover job** (Create). Create a Job. Creates a job in your organization that is ready for photo capture in the Hover app. Hover recommends capture requests (capture_requests.create) over creating jobs directly. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Sent as multipart/form-data (job[name], job[location_line_1] ...), as Hover documents it.
- **Update a Hover job by ID** (Update). Update a Job. Use this endpoint to update the details of a Job’s property or owner. Send only the job fields to change. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: id.
- **Hover jobs archive** (Archive). Archive Job Access. Archives the job access: the job no longer shows in the users' property lists. List Jobs with archived=true still returns it, and Hover can unarchive it later. Required: job_id.
- **Hover jobs assign** (Assign). Re-Assign Requesting User. Use this endpoint to re-assign the requesting user of a Job to a different user. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: user_id, job_id.
- **List all Hover measurements JSON** (List). Get JSON Measurements. This endpoint returns detailed measurement data for a given model_id in JavaScript Object Notation (JSON) format. This is the primary method for pulling structured measurement data directly into your external systems for further analysis, estimation, material ordering, etc. version: summarized_json, full_json, sketch_json or paint_measurements. Required: version, model_id.
- **List all Hover measurements pdfs** (List). Get Measurements PDF. The Measurements PDF provides a detailed, printable report of a property's measurements. This endpoint facilitates retrieving that report for a designated model. Required: model_id. Returns the file (application/pdf), not JSON.
- **List all Hover measurements xlsx** (List). GET XLSX Measurements. This endpoint allows your integration to retrieve measurement data for a given model_id in Microsoft Excel (XLSX) format. It is designed for businesses that require measurement data in a spreadsheet format consumable by Microsoft Excel and other compatible programs. Required: model_id. Returns the file (application/vnd.openxmlformats-officedocument.spreadsheetml.sheet), not JSON.
- **Create a Hover multi structure test job** (Create). Multi-Structure Test Jobs. This endpoint allows a mocked multi-structure test job to be created for development testing; this endpoint does not fire expected webhooks. Development only: creates a mocked multi-structure test job (no webhooks), free of charge. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: job_preset, state.
- **List all Hover notes** (List). List Notes. List all notes associated with a Job. Required: job_id.
- **Create a Hover note** (Create). Create Note. Use this endpoint to create a note for a given Job ID in Hover. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: current_user_email.
- **Update a Hover note by ID** (Update). Update Note. Use this endpoint to update a note on a Job in Hover. Hover's access tokens belong to the organization, so this call names the acting user with current_user_id or current_user_email (an admin user's id from users.list). Required: id, current_user_email.
- **Delete a Hover note by ID** (Delete). Delete Note. This endpoint deletes a note based on the required note_id path parameter. This is an irrevocable action and cannot be reverted. Required: id.
- ...and 22 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
