Cursor reads Housecall Pro through DeepLedger's hosted MCP server: add https://mcp.deepledger.ai/mcp to Cursor's mcp.json, sign in with your DeepLedger account, and Cursor's agent can read the company's Housecall Pro jobs, estimates, invoices and payments next to its QuickBooks or Xero books. The Housecall Pro side is read only. This guide is for bookkeepers and finance people who already work in Cursor, and for whoever builds the firm's monthly checks for home service clients.
Cursor suits work that should leave a file behind: a CSV of unmatched deposits, a list of completed jobs with no invoice, a short note per client for the reviewer. Chat apps answer in the conversation; Cursor's agent can also write the answer into your project.
DeepLedger is an independent integration. It is not affiliated with or endorsed by Housecall Pro. The general Housecall Pro guide, with every tool and limit, is Connect Housecall Pro to your AI agent.
What does Cursor get from Housecall Pro?
DeepLedger gives the AI agent four read-only Housecall Pro tools. Amounts come back in dollars.
| Tool area | What Cursor's agent can read |
|---|---|
| Company and lists | Company name, time zone and locations; customers, employees, job types, tags, lead sources, price book services, materials |
| Jobs | Customer, service city, status, schedule, totals and outstanding balance; a job's line items, invoices, materials and appointments |
| Estimates | Estimates and their options, with totals and approval status; an option's line items |
| Invoices | Amount, amount due, taxes, discounts and payments (method, amount, date); line items on a single invoice |
Customer and employee email addresses and phone numbers, street addresses, notes, attachments and payment notes are left out of every answer. A customer's place comes through as city, state, zip and country. Text your staff typed into job or line item descriptions comes through as written, so treat a file Cursor writes from it like any other client workpaper.
Each call reads, answers and keeps no Housecall Pro records. DeepLedger keeps only the saved key, encrypted.
Before you start
- Housecall Pro API access. Housecall Pro names the MAX plan for API keys; XL is listed on its API page too (as of November 2026). An admin in Housecall Pro creates the key.
- Housecall Pro's permission for this connection. Housecall Pro's API terms set rules for apps built on its API, including how API keys are shared. Check that Housecall Pro allows this connection for your account before you connect.
- A DeepLedger account with the company set up, usually with QuickBooks Online or Xero already connected, and an owner or admin to paste the key.
- Cursor desktop. On Enterprise, admins can restrict which MCP servers and tools are allowed.
- A project folder for the output files, kept out of any public repository.
How do I connect Housecall Pro to Cursor?
- Connect Housecall Pro in DeepLedger. A Housecall Pro admin generates a Read-only API key under API Key Management. A DeepLedger owner or admin opens Companies, chooses the company, then Connections, then Housecall Pro, pastes the key and confirms it was generated as Read-only.
- Add DeepLedger to mcp.json. Add the DeepLedger entry to ~/.cursor/mcp.json for all projects or .cursor/mcp.json for one project, keeping any servers already there.
{
"mcpServers": {
"deepledger": {
"url": "https://mcp.deepledger.ai/mcp"
}
}
}
- Enable the server and sign in. Open the Customize page in Cursor's sidebar, turn on DeepLedger and sign in with your DeepLedger account, not your Housecall Pro login.
- Check the connection. In Agent chat, ask: Using DeepLedger, which company am I in? Read the Housecall Pro company and tell me its name and time zone.
If DeepLedger is already in your mcp.json for QuickBooks or Xero, skip steps 2 and 3: the same entry reaches Housecall Pro once the company has it connected. The file locations and OAuth support follow Cursor's MCP documentation. DeepLedger supports dynamic client registration, so there is no client ID to paste.
If the company name in the answer is not the business you expected, the key belongs to another Housecall Pro account. An owner or admin disconnects it on the company's Connections tab and pastes the right one.
When a browser sign-in is not possible
Create a DeepLedger API key under Settings → API keys → Create key, choose All my companies or One company, and set it as DEEPLEDGER_API_KEY in the environment Cursor starts from:
{
"mcpServers": {
"deepledger": {
"url": "https://mcp.deepledger.ai/mcp",
"headers": {
"Authorization": "Bearer ${env:DEEPLEDGER_API_KEY}"
}
}
}
}
The DeepLedger key acts as the person who created it, with that person's access to every connected app, the ledger included. It has no read-only setting of its own; the Housecall Pro tools are reads whatever key you use. Never paste the key itself into a project file that may be committed.
Checks that leave a file behind
Name the company in each prompt and start with "do not change anything". Cursor's agent then reads both sides and writes what it finds. The examples use a fictional business, Bright Path Plumbing.
Deposits by day, as a CSV
In Bright Path Plumbing, do not change anything. Read Housecall Pro invoices paid in October 2026 with each payment's method, amount and date. Total them by day and by method, then read the bank deposits in the books for the same days. Write
bright-path/2026-10-deposits.csvwith date, method, Housecall Pro total, deposit total and difference.
Card payments often reach the bank as one deposit for several invoices, less fees, so a difference on a card day is a lead, not an error. If the books hold payments in Undeposited Funds first, ask for that account too.
Completed jobs with no invoice
List Housecall Pro jobs scheduled in October 2026 with status and outstanding balance. For each completed job, read its invoices. Write
bright-path/2026-10-uninvoiced-jobs.mdwith a table of completed jobs that have no invoice: job, customer city, scheduled date and total.
Receivables on both sides
List Housecall Pro invoices that are open or pending payment, with job, due date and amount due. Read the AR aging in the books as of today. Write one table by customer with both totals and the difference to
bright-path/ar-compare.csv, and tell me the five largest differences in chat.
A reviewer's summary
Read the three files in
bright-path/and writebright-path/review-notes.md: one line per difference with customer, side, document, amount and the likely cause. Do not change anything in Housecall Pro or the books.
Keep the prompts that work in a markdown file in the project, one per check, so next month starts from the same wording. For the rest of the close, see the QuickBooks month-end close checklist or the Xero month-end close checklist.
What Cursor cannot do here
- Change Housecall Pro. Every Housecall Pro tool is a read. DeepLedger sends Housecall Pro only read requests, to a fixed list of routes, and refuses any other request before it is sent. That rule is DeepLedger's own, so it holds whatever the key allows.
- See contact details. The fields listed above never reach Cursor.
- Run on its own. Nothing reads Housecall Pro until you ask in Agent chat.
The ledger side is different: DeepLedger's QuickBooks and Xero tools include writes. Since Cursor 3.6 the default run mode, under Settings → Agents → Approvals & Execution, is Auto-review: allowlisted MCP tools run at once and the rest go to a classifier, which Cursor says is not a security boundary and can let a call run that you would have stopped. To keep every ledger write asking, choose Allowlist and allowlist only read tools. Housecall Pro reads may run through DeepLedger's own read tool, titled DeepLedger: Run a Read Tool, which only reads but covers every app DeepLedger reads that way. Cursor's run modes page explains each mode.
Troubleshooting
DeepLedger is missing from Cursor. Check the JSON is valid and in the right file, restart Cursor, and turn DeepLedger on from the Customize page in Cursor's sidebar. The MCP Logs in Cursor's Output panel show why a server did not start.
The agent says it has no Housecall Pro tool. DeepLedger offers the Housecall Pro tools when you ask for Housecall Pro data. Ask: Using DeepLedger, list this company's connections, then read Housecall Pro jobs. If Housecall Pro is not listed, check the company's Connections tab.
Housecall Pro needs reconnecting. The key was deleted or no longer works. Generate a new Read-only key and paste it on the company's Connections tab.
A location's jobs are missing. A Housecall Pro key reaches its own location and the locations beneath it. Ask the agent to list the company's locations and read the missing one by name.
Authentication fails with an API key. Check that DEEPLEDGER_API_KEY is set in the environment Cursor was started from, starts with dl_live_, and has not expired or been revoked.
A long list stops early. Large lists come in pages. Ask for a narrower date range or one customer.
Is it safe?
- Each developer signs in as themselves. The OAuth sign-in ties Cursor to your DeepLedger login, so it reaches only the companies you are assigned to; owners and admins see every company.
- Two fences on Housecall Pro. DeepLedger sends only read requests, and the Read-only key is a second fence.
- Revoking access. Disconnect Housecall Pro on the company's Connections tab, or delete the key in Housecall Pro's API Key Management. Remove DeepLedger from
mcp.json, and revoke the grant under Settings → Connected apps or the API key in DeepLedger, to stop Cursor everywhere.
Frequently asked questions
How do I connect Housecall Pro to Cursor?
Connect Housecall Pro to the company in DeepLedger with a Read-only API key, then add https://mcp.deepledger.ai/mcp to Cursor's mcp.json, enable DeepLedger in Cursor and sign in with your DeepLedger account. Cursor's agent then reads Housecall Pro through DeepLedger.
Can Cursor change anything in Housecall Pro?
No. Cursor's agent can write files in your project, but not to Housecall Pro. DeepLedger sends Housecall Pro only read requests and refuses any other request before it is sent, so no customer, job, estimate or invoice in Housecall Pro can be created, edited or deleted from Cursor.
Do I need an API key in Cursor?
No, not for Cursor on your own computer. DeepLedger supports OAuth sign-in, so the mcp.json entry needs only the URL. A DeepLedger API key in an Authorization header is for setups where a browser sign-in is not possible.
Does Cursor see my Housecall Pro API key?
No. The Housecall Pro key is saved in DeepLedger, encrypted and tied to one company. It is never shown again, never logged and never sent to the AI agent. Cursor signs in to DeepLedger, not to Housecall Pro.
Where do the results go?
Wherever you ask. Cursor's agent can answer in chat or write a table into a file in your project, such as a CSV of differences for a reviewer. DeepLedger keeps no Housecall Pro records; each call reads, answers and keeps nothing.
Related guides
- Connect Housecall Pro to your AI agent
- Connect Cursor to QuickBooks Online
- Connect Cursor to Xero
- Connect Housecall Pro to Claude
See every supported app on AI platforms and integrations.