Gusto MCP: connect Gusto to Claude and ChatGPT
Ask Claude or ChatGPT who joined in October, how many people each department has or whether this month’s payroll has been processed. The answer comes straight from Gusto, without a report or a message to HR.
We build the connector for your company on Gusto, next to your other systems. It only reads, your company decides which groups get it, and payroll data is sensitive, so salary details stay out unless you choose otherwise.
Built for your company · Works in Claude, ChatGPT and Copilot
What your team can do with Gusto in Claude and ChatGPT
Headcount without a report
Your team at a glance
Where the payroll stands
People data next to the rest
Ask it like this
“Who joined the company in October, and which department are they in?”
“How many employees and contractors do we have in each department?”
“Has the payroll for the second half of October been processed?”
“Which people on Megan Walsh’s team start before the end of the year?”
“List the contractors we have worked with this quarter.”
“How much paid time off does each person in the Denver office have left?”
What we build for Gusto
Deployed OS has no ready Gusto connector yet. We build it for your company when you start, on Gusto’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.
- Employees and contractors
- People with the details your company allows, such as job title, department, location, manager and start date.
- Departments and locations
- Your departments and work locations, so the AI can group people the way your company does.
- Payroll status
- Pay runs with their pay periods and whether they are processed. Amounts and pay stubs stay out unless you ask for them.
- Time off
- Time off policies and balances, read per person and team.
Who sees what
- Read-only
- The connector reads. It does not run payroll, change pay, add employees or approve time off.
- A company connection, access per group
- A Gusto admin authorises the connection once for the company, so people do not sign in with their own Gusto login. Deployed OS decides who may use it: admins choose which groups get Gusto, and a group without access never sees the connector.
- Salary data kept apart
- Compensation, pay stubs and tax details stay out of the connector unless you decide otherwise, and then only for the groups you name, such as payroll or finance.
- Every call logged
- Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Set up the Gusto connector in three steps
Gusto’s own MCP server or Deployed OS?
Gusto has its own MCP server for Claude, ChatGPT and other MCP clients. It needs a primary or global admin in Gusto, and the connection works with that admin’s permissions. It queries payroll and people data, and eligible customers can also run payroll from Claude. Gusto advises confirming every tool call before it runs. For a founder or payroll admin who wants Gusto in their own AI tool, it is a good fit.
Deployed OS is for when more people than your Gusto admins need answers, or Gusto is one system among several. We can build company-specific tools on top, such as a headcount view for managers that leaves pay out. Admins decide which groups get Gusto, every call is logged in one place, and the same rules apply in Claude and ChatGPT, next to your company’s skills and guardrails.
Gusto MCP: common questions
Yes. Gusto has its own MCP server for Claude and ChatGPT. It needs primary or global admin permissions in Gusto and works with that admin’s access. Deployed OS adds Gusto to one company connection with your other systems, with read access per group, salary data kept apart and one log.
Not through the connector we build. It reads people, departments, payroll status and time off. It does not run payroll, change pay or edit employee records.
Nobody, unless you decide otherwise. We leave compensation, pay stubs and tax details out of the connector. If pay should be readable, we keep it to the groups you name, such as payroll or finance, and every call is logged.
No. A Gusto admin authorises the connection for the company, so the connector cannot apply each person’s own Gusto permissions. Access is set in Deployed OS instead: which groups get Gusto, and which data the connector may read at all.
Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Gusto data is fetched when someone asks for it.
It depends on the size of your team. Get in touch and we will walk you through it.
See it on your own tools.
Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.