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.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which capture requests from this week are still waiting on photos?
Working in Hover with Elaichi
-
Get single Hover agreement by ID
-
Get single Hover capture request link by ID
-
List all Hover capture requests
How to connect Hover to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Hover MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Hover MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Hover through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Hover is logged.
-
Sales
Order a capture before the sales call
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.
-
Estimating
Pull the estimate into the proposal
Look up the estimate for a job and have the numbers explained in plain language, then create the order document once the homeowner signs.
-
Production
Fix a measurement before the crew goes
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.
-
Claims
Hand the inspection to the adjuster
Share the inspection workflow, pull the inspection PDF and the photos, and answer the adjuster's question without opening the job yourself.
-
Design
Start a blueprint from the capture
Create a blueprint once the deliverable lands, then list the floor plan wireframes and exports the design team needs for the drawing set.
-
Office
Check the agreement before you invoice
Look up the agreement for a job and list the estimates and deliverables tied to it so the invoice matches what was actually ordered.
Try asking
- “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.”
What connecting Hover gets you
6 screens from Elaichi, each doing one job for your Hover account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about capture requests in plain words.
Get answers from live Hover deliverables and estimates without opening a single job.
Copy the endpoint
AI apps
One Hover endpoint, every client, no shared key.
Claude, ChatGPT and Cursor reach Hover through one governed endpoint with no SDK.
Tool catalog
72 Hover tools, ready with no code.
Capture requests, deliverables, estimates and inspections, covered without writing a line of code.
Toolboxes
Every team gets its own Hover toolbox.
Sales sees capture requests, estimating sees deliverables, each team scoped to its own work.
Shared connections
Teammates use Hover without touching a credential.
One person connects Hover, shares it with teams, and nobody else sees a secret.
Audit log
Know who changed every Hover capture request.
When, who, what happened and which record, kept in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Hover digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch capture requests
Hover
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Hover
Queued
Workflows
A schedule drafts the Hover digest itself.
New deliverables are fetched, grouped, drafted, approved by a person, then posted back to Hover.
Hover health
Refreshed 4 minutes ago · every 15 minutes · from the capture requests collection
Capture requests
1,284 ↓ 12%
Deliverables
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Capture requests created
Last 14 days
By team
Share of activity
Sales East 34%
Sales West 27%
Estimating 21%
Production 18%
Collections and dashboards
Hover numbers computed, not asked for.
Capture requests created over 14 days, split by team, refreshed on a schedule with no model.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Hover tools for your AI agents
72 tools are ready to call through Elaichi's MCP endpoint the moment you connect Hover, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Hover in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot