Housecall Pro MCP connector
Connect Housecall Pro once in Elaichi and Claude, ChatGPT, Cursor, and the Elaichi Agent can look up customers, create and dispatch jobs, add line items and notes, draft estimates, and read invoices under each person's own access.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Housecall Pro to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Housecall Pro once
-
Open Connections, choose Add connection, and pick Housecall Pro.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Housecall Pro API key. One person generates a token in Housecall Pro and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Housecall Pro 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.
Housecall Pro 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 today. The plugin directory lives at chatgpt.com/plugins.
Housecall Pro 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.
Connect Housecall Pro 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.
Use cases
What teams do with Housecall Pro through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Dispatch
Book and dispatch a job from a call
A customer calls about a leaking water heater and the dispatcher asks for a job to be created at their address and sent to the nearest available technician. The job lands on the board without anyone leaving the phone.
-
Office
Add a new customer and service address
When a first-time caller books, the office adds the customer and their service address to Housecall Pro by describing it in plain words. Repeat callers are found by name or phone number before anything is duplicated.
-
Sales
Draft an estimate while the lead is warm
After a site visit, the salesperson asks for an estimate for the furnace replacement they just scoped. It is ready to review before they are back in the truck.
-
Finance
See which invoices are still open
Billing asks which invoices from last week have not been paid and gets the list with amounts and customers. A preview of any single invoice is a question away.
-
Field
Catch the job up after the visit
Technicians add the parts they used as line items and leave a note about what they found, so the office sees the full picture before invoicing.
-
Management
Lock finished jobs at week's end
The owner asks to lock every completed job from the week so nobody edits line items after the numbers have been reviewed.
Try asking
- “Dispatch the 2 pm water heater job to Marco.”
- “Draft an estimate for the Hendersons' furnace replacement.”
- “Which invoices from last week are still unpaid?”
Compare
Elaichi vs Zapier MCP vs Composio for Housecall Pro
All three can connect Housecall Pro 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 Housecall Pro tools | Allow or restrict single Housecall Pro 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 Housecall Pro 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 | $15 per user per month. | 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.
AI tools
Housecall Pro tools for your AI agents
95 tools are ready to call through Elaichi's MCP endpoint the moment you connect Housecall Pro, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Housecall Pro gets you
6 screens from the product, each doing one job for your Housecall Pro account.
The agent
Ask about today's jobs in plain language.
Get answers from live Housecall Pro customers, jobs and invoices without opening the app.
- customers
- jobs
- invoices
- estimates
Ask Elaichi to work across your apps.
Dispatch the 2 pm water heater job to Marco.
Draft an estimate for the Hendersons' furnace replacement.
Which invoices from last week are still unpaid?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint for Claude, ChatGPT and Cursor.
Connect Housecall Pro once and every MCP client uses it, with no shared API key.
Copy the endpoint
Tool catalog
95 Housecall Pro tools, no custom code.
Customers, addresses, jobs, line items, notes, estimates and invoices, ready without writing anything.
- Create a Housecall Pro customer address
- Get single Housecall Pro customer address by ID
- List all Housecall Pro customer addresses
- Create a Housecall Pro customer
Toolboxes
Each team gets its own Housecall Pro toolbox.
Dispatch handles jobs, billing sees invoices, and the office keeps customers current, scoped per team.
- Dispatch
- Office
- Sales
- Billing
Shared connections
Share one Housecall Pro connection, keep the key.
Teammates book and dispatch jobs through a shared connection without ever seeing the API key.
- Dispatch
- Office
- Sales
- Billing
Audit log
Every job change is logged with a name.
See who dispatched a job, edited a line item or locked it, and exactly when.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the morning dispatch digest.
Jobs are fetched, grouped by technician, drafted into a digest, approved, then posted to Housecall Pro.
Housecall Pro digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch customers
Housecall Pro
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 Michael Brennan
Approve Deny -
Post the digest
Housecall Pro
Queued
Collections and dashboards
Job volume reported without asking anyone.
Four metrics, 14 days of jobs created and a team breakdown, refreshed on a schedule.
Housecall Pro health
Refreshed 4 minutes ago · every 15 minutes · from the customers collection
Customers
1,284 ↓ 12%
Jobs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Customers created
Last 14 days
By team
Share of activity
Dispatch 34%
Office 27%
Sales 21%
Billing 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Housecall Pro to Claude?
First connect Housecall Pro in Elaichi by pasting your Housecall Pro API key, which you can copy from your Housecall Pro account settings. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi and Housecall Pro is ready.
Does Housecall Pro work with ChatGPT and Cursor as well as Claude?
Yes. Once Housecall Pro is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Housecall Pro once and every client uses it.
What can an AI agent actually do with my Housecall Pro data?
An agent connected to Housecall Pro can find a customer by name, add a new customer and service address, create a job and dispatch it to a technician, add line items and notes to a job, draft an estimate, and look up invoices including a preview of a single one. Short concrete asks work best, such as asking it to dispatch the 2 pm job to Marco rather than writing a long paragraph.
Does connecting Housecall Pro give the AI access to every job and customer?
The AI only sees what the person who signed in can see in Housecall Pro, because every call runs under that person's own access. Elaichi can narrow that further by restricting specific actions, but it can never widen it. Someone who cannot lock jobs in Housecall Pro cannot lock them through Claude either.
Can I stop an agent from deleting or changing things in Housecall Pro?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Housecall Pro jobs and invoices while blocking deleting line items or notes. A restricted action is left out of the AI client's list entirely and cannot be called, whatever the prompt says.
What happens to a Housecall Pro connection when someone leaves?
Offboarding a person in Elaichi ends their access to Housecall Pro through every AI client at once. A shared Housecall Pro connection keeps working for everyone else on the team. If you want to remove Housecall Pro altogether, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Housecall Pro MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Housecall Pro 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, 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 Housecall Pro?
Yes. Both let Claude, ChatGPT or Cursor use Housecall Pro. 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 Housecall Pro call.
How is Elaichi different from Composio for Housecall Pro?
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 Housecall Pro: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Housecall Pro in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.