Connect Gusto to Claude Code

Have Claude onboard hires and prep payroll in Gusto. From the terminal, inside the sessions where you already work.

How do you connect Gusto to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Gusto, you add a Gusto MCP server: a small hosted service that exposes Gusto's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Gusto account. No API keys pasted into config files.

claude mcp add --transport http gusto https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Gusto once connected?

A custom connector adds the write actions the native read-only tools leave out. Claude can add a new hire and start onboarding, update an employee's pay rate, file or approve time-off requests, adjust deductions, and stage a payroll run for your review. The record-keeping that used to mean clicking through forms happens where your people data already lives.

Create a new employee and kick off their onboarding flow
Update an employee's compensation or pay rate
Enter or approve a time-off or PTO request
Adjust benefit deductions or contribution amounts for an employee
Stage a payroll run with hours and earnings for your review
Update an employee's job title, department, or home address

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Gusto access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Gusto API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Gusto changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Gusto connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Gusto connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Gusto account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Gusto's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Gusto?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Gusto account it signs in with. Revoking access is one click in Gusto.

More on the Gusto connector

Gusto connector for claude.ai BambooHR + Claude Code Rippling + Claude Code Workday + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us