Houzz Pro MCP Server
Houzz Pro'da potansiyel müşteriler, projeler, teklifler ve faturalar.
Barındırılan MCP Sunucusu
npx add-mcp 'https://cotlet.dev/mcp/v1/houzz-pro'Claude Code, Codex, Cursor ve daha fazlasına kurulur
Dokümantasyon
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
Houzz Pro API and MCP server: Let your AI agent run your Houzz Pro back office.
Houzz Pro has no public API, no webhooks and no MCP server for its back office (checked 24 Oct 2026). Cotlet runs 14 Houzz Pro tools hosted, over MCP for agents and REST for scripts.
Bring Houzz Pro leads, projects and tasks into your AI agent or operations report. Use MCP or REST from n8n, Make, Zapier and scripts.
- Free 7-day trial, no card
- Unofficial, not affiliated with Houzz
- Page: https://cotlet.dev/integrations/houzz-pro-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Houzz Pro. Houzz Pro is a trademark of its owner. If Houzz Pro's own integrations cover what you need, use them first.
What can you automate in Houzz Pro?
- Add leads from your web forms
- Chase leads that went quiet
- Convert a won lead to a project
- Build and send estimates
- Bill the next draw
- Log crew hours
Does Houzz Pro have an MCP server or an API?
- The Zapier app has 2 actions, Create Lead and Create Project, and no triggers. Houzz calls it one-way, offers it on select packages only, and it fails for a pro in more than one Houzz Pro team.
- Zapier MCP for Houzz Pro has the same 2 actions, at 2 Zapier tasks per call.
- QuickBooks Online and Gusto take invoices and hours out of Houzz Pro. Nothing official reads leads, moves stages or sends an estimate.
| What you need | Zapier (select packages) | Custom build (Supergood) | Cotlet |
|---|---|---|---|
| Add leads and projects | Yes | If they build it | Yes |
| Read leads, tasks, estimates and invoices | No | If they build it | Yes |
| Move stages and convert a won lead | No | If they build it | Yes |
| Estimates, draws and invoice sends | No | If they build it | Yes, sends after your OK |
| Your Houzz password stays with you | Yes | No, they log in with it | Yes, you sign in yourself |
Checked 24 Oct 2026. Sources: Houzz Pro: How to integrate Zapier, Zapier: Houzz Pro integrations, Supergood API Report Card: Houzz Pro, Houzz Pro integrations
How does Cotlet connect to Houzz Pro?
- Sign in to Houzz Pro. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your Houzz password, and no estimate or invoice reaches a homeowner until you approve it.
Connect Houzz Pro to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Enable Houzz Pro for agents. Create a Cotlet account, sign in to Houzz Pro in its Cloud Browser and press Enable for agents.
- Give your agent the address. Add https://cotlet.dev/mcp/v1 to the MCP servers or connectors of your AI agent.
- Confirm who you are. Chat apps open a Cotlet sign-in. Code editors, n8n and scripts send an API key made in the console.
Houzz Pro shares https://cotlet.dev/mcp/v1 with every other app you enable on Cotlet. Turned on Houzz Pro after you connected? Refresh the connector and the 14 tools appear.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-houzz-pro \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-houzz-pro": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-houzz-pro]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: houzz_pro_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: houzz_pro_write
How to use the Houzz Pro REST API
Create your Cotlet API key
Create a Cotlet API key with access to Houzz Pro and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Sign in to Houzz Pro in its Cotlet Cloud Browser and enable the app for agents. Your Houzz Pro role determines the projects and records you can read.
Make your first Houzz Pro API request
REST:
curl "https://cotlet.dev/api/v1/houzz-pro/leads?limit=2" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read leads and continue the pipeline
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "houzz-pro",
"tool": "list_leads",
"result": {
"leads": [
{
"lead_id": "lead_20418",
"lead_name": "Miller Kitchen",
"stage": "Proposal/Estimate Sent",
"client_name": "Dana Miller",
"location": "Austin, TX",
"project_type": "Kitchen remodel",
"lead_source": "Website",
"tags": [
"Spring"
],
"estimated_revenue": 29500,
"last_activity": "2026-09-24T15:10:00Z"
}
],
"next_cursor": null
}
}
Read result.leads and pass result.next_cursor unchanged as cursor until null. Preserve stage, query, source, tags and limit while paging.
Lead pages default to 50 records, with a maximum of 100, newest first. Compare stage, last activity and estimated revenue as well as lead IDs.
Project invoice and estimate reads need a project_id. Use IDs from your own project list rather than guessing them.
Houzz Pro workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Combine leads and lead details into a follow-up review sheet with stage and last activity. |
| Make | HTTP > Make a request | Read projects and tasks into a daily project briefing for your chosen destination. |
| Python or Node.js | REST API | Combine project estimates and invoices into a commercial review without sending documents. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads Houzz Pro; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
Houzz Pro API endpoints and MCP tools
Leads and pipeline
Default and custom stages, up to 100 leads a page. A converted lead never turns back into a lead, so conversion asks first.
- List leads (
list_leads, read): Leads with stage, client, location, project type, source, tags and last activity. - Get lead (
get_lead, read): Full lead: client contact, address, description, estimated revenue and profit, notes and tasks. - Create lead (
create_lead, write): New lead in your pipeline. - Update lead stage (
update_lead_stage, write): Move a lead to another stage of your pipeline. - Convert lead to project (
convert_lead_to_project, write, asks first): Turn a won lead into a project; the lead address becomes the project address. Cannot be undone.
Projects, tasks and time
Tasks go to your team and subs, never to a client. Time for someone else needs the Time Management permission.
- List projects (
list_projects, read): Projects with client, address and status. - List tasks (
list_tasks, read): Tasks from the Task Center, sorted by due date, with assignee and status. - Create task (
create_task, write): Task on a project or lead, assigned to a team member, client or sub. - Log time (
log_time, write): Time entry on a project; rate, markup and billable status come from the activity.
Estimates and invoices
Drafts stay inside Houzz Pro. Only send_document emails the homeowner, and only it can issue an invoice.
- List estimates (
list_estimates, read): Estimates of a project with title, total and client approval. - Create estimate (
create_estimate, write): Draft estimate on a project from line items. Nothing reaches the client until you send it. - List invoices (
list_invoices, read): Invoices of a project with code, total, status and payments received. - Create invoice (
create_invoice, write): Draft invoice from an estimate: the whole document, selected line items or a percentage. - Send document (
send_document, write, asks first): Email an estimate or invoice to the client to view, approve or pay online.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/houzz-pro-api-mcp-server#tools
Who can see my Houzz Pro session, and how do I revoke it?
- What we store. Your signed-in Houzz Pro profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 14 Houzz Pro tools. No cookie, no login.
- What the session sees. What your Houzz Pro seat sees: leads, homeowner contacts, estimates, invoices, crew time.
- What no tool touches. Online payments, QuickBooks settings, your plan, users and deletes.
- If Houzz signs you out. We email you a link to sign in again. We never type your password.
- How to cut access. Disable for agents, reset the browser or delete the API key. The next call fails.
Cotlet scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Finds the approved estimate. Two approved on one project? It asks which.
- Adds up past draws. Stops if the draw would pass what is left.
- Drafts the invoice. A percentage or the line items of one phase.
- Waits for your OK. The send shows up in your Cotlet console.
| Action | Undo |
|---|---|
| Convert a lead to a project | No, a project never goes back to a lead |
| Send an estimate or invoice | No, the homeowner has the email |
| Issue an invoice on send | No, it locks and syncs to QuickBooks Online |
| Move a lead stage | Move it back; that lead stops updating on its own |
| Create a task | Delete it; the assignee already got an email |
| Log time | Edit it, unless an issued invoice uses it |
2 of 14 tools ask first: convert_lead_to_project, which cannot be undone, and send_document, the one that emails a homeowner. Drafts, tasks, stages and time entries reach no client and run at once. Switch the wait off per tool for a scheduled run.
issue_on_send stays off unless your prompt asks for it, since an issued invoice is locked.
MCP call:
{
"name": "create_invoice",
"arguments": {
"estimate_id": "est_48213",
"percent": 30
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/houzz-pro/estimates/est_48213/invoices \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"percent":30}'
Tool output:
{
"invoice_id": "inv_77105",
"code": "INV-0012",
"project": "Oak Street Kitchen",
"status": "draft",
"subtotal": 8850,
"currency": "USD"
}
Cron jobs and scripts call the same tools over REST at /api/v1/houzz-pro, one key and one price for both. Logging time for a teammate without the Time Management permission fails, and a failed call costs nothing. The tools table lists the REST path of each tool.
How much does the Houzz Pro MCP server cost?
About $18 a month for a five-person remodeling firm, 3,130 credits. Your Houzz Pro plan stays billed by Houzz.
| Job | Calls | Credits |
|---|---|---|
| Add web form leads, weekly | 4 × 4 | 160 |
| Task the leads that went quiet, weekly | 9 × 4 | 360 |
| Mark a lead Won and convert it | 3 × 1 | 30 |
| Build and send an estimate | 3 × 3 | 90 |
| Bill the next draw on a project | 5 × 3 | 150 |
| Log crew hours from the chat, weekly | 21 × 4 | 840 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 3,130 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on the Design, Pro and Teams plans
The firm is the NAHB 2025 median for remodelers: 5 people and 12 jobs a year of $10,000 or more. Leads, draws and crew hours are our assumption: 10 leads a month, 3 projects billed in draws, 4 crew logging a day each. Crew hours are half the bill. Dollars at the $29 pack rate.
Houzz Pro MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| hanbiji/Houzz-Api | Python wrapper of the Houzz Marketplace seller API, 7 stars. | Product listings only, no Houzz Pro data; last commit 22 Apr 2017. |
| Houzz scrapers on GitHub and Apify | About 20 scrapers of public pro profiles, reviews and products. The largest Apify actor has 295 users. | Public directory only. Nothing from your leads, estimates or invoices. |
| Supergood | Builds a custom unofficial API and MCP for a Houzz Pro account. | Sold after a sales call, no public price, logs in with your password. |
| Buildertrend, JobTread | Construction software with more official integrations. | You move your leads, projects and estimates off Houzz Pro. |
No GitHub project and no Houzz partner offers a Houzz Pro MCP server today. Zapier is enough if all you need is web leads landing in Houzz Pro. Cotlet is for an agent that also reads the pipeline, prepares estimates and draws, and logs time.
Who runs Cotlet
Behind Cotlet is Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Houzz Pro tools go to contact@cotlet.dev.
Houzz Pro API and MCP: questions
Can I use the Houzz Pro API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
How do I get access?
Make a free account at https://cotlet.dev, open Houzz Pro under Integrations in the console and sign in to Houzz Pro in its Cloud Browser. The trial starts when you sign up, and no card is asked.
How do I connect Houzz Pro to ChatGPT or Claude?
Sign up at cotlet.dev, log in to Houzz Pro once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Houzz Pro account through Cotlet, in their phone apps too.
What can ChatGPT do in Houzz Pro?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Houzz Pro: import leads from a spreadsheet; follow up on stale leads; mark a lead won and convert it to a project. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need a Houzz Pro package with Zapier?
No. Cotlet works in your own Houzz Pro account and does not use the Zapier app, which Houzz Pro offers on select packages only (checked 11 Oct 2026). Logging time for other team members needs the Time Management permission.
Can my agent send an estimate or invoice on its own?
Only if you switch confirmation off for send_document. By default you confirm each send; drafts from create_estimate and create_invoice reach no client.
Does Houzz Pro have webhooks?
No. Houzz Pro sends no events out, and its Zapier app has no triggers. To act on new leads or a quiet pipeline, run your agent on a schedule, for example list_leads every Monday morning.
Which Houzz Pro plan do I need?
Any of Design, Pro or Teams. Cotlet works in your own seat and adds no user. What your plan lacks stays missing: schedules, change orders and daily logs start on Pro, for example.
Does it touch QuickBooks Online?
No. Houzz Pro syncs issued invoices to QuickBooks Online by itself. The agent only decides whether an invoice is issued on send, and leaves that off unless you ask.
Is the MCP server different from the REST API?
Only the way in. Both carry the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with Houzz?
No. Cotlet is independent and not affiliated with Houzz Inc.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.