We built an MCP server for Payaca. Here's what it lets your team do.
Connect your AI assistant straight to your Payaca account and ask it to do real work: pull stuck jobs, bulk-update projects, draft follow-ups, build reports. Here's why we built it and the practical things install teams can do with it.
Payaca is the operations platform for clean tech installation businesses.Book a demo →
Matt Franklin
CEO & Founder·June 4, 2026·Last updated: July 4, 2026
The Payaca MCP server connects your own AI assistant (Claude and others) directly to your Payaca account.
It can read and act on your data the same way Agent Dave does: find jobs, update projects, draft notes, build reports.
It turns "can someone pull me a list of..." into a question you ask in plain English and get an answer to in seconds.
It acts as you, with your permissions. It is only as good as the data already in your account.
It is live now. If you are on Payaca, you can add it as a connector in your AI assistant and authorise it with your login today.
We shipped an MCP server for Payaca. It lets you connect your own AI assistant to your account and ask it to do real work: find the jobs stuck waiting on a grid connection, tag every project from last month's import, draft a follow-up note, pull a conversion report. You ask in plain English. It does it in your account.
If you have used Agent Dave, this is the same engine. Dave is the assistant inside Payaca - you ask it to look things up, update records, and create events without leaving the app. The MCP server hands that same ability to whatever AI client you already use, so the conversation can happen wherever you already work.
See it on your own data
The fastest way to understand this is to watch it run against a real account. Book a 20-minute demo and we'll connect it live and answer the questions you actually ask your ops team every week.
Every growing install business runs on a steady stream of small questions. Which jobs are waiting on the DNO. Who hasn't been invoiced. What converted last quarter and what didn't. Which customers are due a service reminder.
Most of those questions have an answer sitting in your system. The problem is getting it out. Today that usually means someone exports a CSV, opens a spreadsheet, and spends twenty minutes turning data into the thing you actually asked for. Or it becomes a request to your software provider to build a report, and you wait.
We did not want to build a report for every question an installer could ever ask. That road never ends, and most of the questions are one-offs anyway. So we did the other thing: we made the account itself something you can talk to.
MCP is an open standard for connecting AI assistants to real systems. We built Payaca's server on it deliberately. It means your account is not a walled garden. You bring the AI client you already use, point it at Payaca, and it can work with your data directly. No export, no waiting on us.
The point is not the technology. It is the everyday operational jobs it takes off your plate. Here are the ones we expect install teams to reach for first.
This is a powerful tool, so it is worth being clear about what it is and is not.
It acts as you. It uses your login and your permissions. It cannot see or do anything in Payaca that you could not see or do yourself.
It is only as good as your data. If your pipeline stages are inconsistent or half your jobs are missing a value, the answers will reflect that. The flip side is that using it tends to surface exactly those gaps, which is no bad thing.
Review before you commit a bulk change. When you ask it to update fifty projects, look at what it is about to do before you say yes. It is fast, and fast is worth a glance.
It is a tool for your team, not a replacement for knowing your business. It gets the data work out of the way so the people who understand the work can spend their time on it.
For years, getting an answer out of your business software meant either knowing where to click or asking someone who did. Software vendors decided which questions were worth a button and which were not.
That model is ending. When your account is something you can talk to, the set of questions you can ask is no longer fixed by what we thought to build. You ask the question you have, today, and you get the answer.
Agent Dave was the first step: AI doing the operational work inside Payaca on its own. The MCP server is the second: that same ability, in your hands, on demand. We are building Payaca to be AI-native from the data up, not an old system with a chatbot bolted on the side.
It's live now
If you're already on Payaca, you can add the MCP server as a connector in your AI assistant, authorise it with your login, and start using it today. If you're not, book a demo and we'll show you what it does with the questions your team asks every week.
Ready to streamline your operations?
See how Payaca helps clean tech installers save time and grow their business.
July's Clean Flexibility Roadmap update sets dates that will reach installers' quotes: minimum standards for smart batteries later in 2026, a Smart Readiness EPC metric in 2027, and a landlord deadline in 2030. What to do about each.
Bulk-bought stock used to land its whole cost on one unlucky project. Payaca's Stock Locations, now live on every account, hold it at real weighted average cost until a job actually uses it.
US solar installers don't have one national permitting clock - they have as many as they have AHJs. Here's what that variance actually costs a growing install business, backed by NREL data.