Gusto MCP server, Claude connector and ChatGPT app: what it does, access and how to connect

Gusto hosts one official MCP server (mcp.api.gusto.com) for its Claude connector and ChatGPT app. It reads and writes, including payroll submission. Admin OAuth. Verified 21 Oct 2026.

Official remote MCP · read & write
Claude connector and ChatGPT app · read & write

Hosting: Remote HTTP, hosted by Gusto (https://mcp.api.gusto.com; the Claude directory connector uses https://mcp.api.gusto.com/anthropic); no local server
Auth: OAuth 2.0 with PKCE; you pick the company and the data categories to share during sign-in
Read / write: Read and write: payroll can be updated and submitted, time recorded and people added once you confirm the call
Works with: Claude.ai, Claude Desktop, ChatGPT, Cursor and Gemini CLI per Gusto; other remote MCP clients, including Claude Code, via the URL
Plan requirement: Gusto global/full admin; Gusto lists Claude Pro or Max and Cursor Pro+. Running payroll in Claude is for eligible customers (per the Claude listing)
Last changed: Sep 2026: report tools (payroll journal, cash requirements, contractor payments) and R&D credit tools added
Verification: Verified 21 Oct 2026 by theFinanceStack · confidence: high

What can an agent do with Gusto through MCP?

Read payroll, employee, contractor, time and pay-schedule data, and act on it: update and submit an unprocessed payroll, record time, add or update people, set an S-Corp owner's W-2 salary from Gusto's estimate and start company onboarding filings.

Gusto says its MCP server has 72 tools, most of them reads: people, compensation, contractors, payrolls, time, pay schedules and reports. The Claude directory listing shows 62 tools for the Claude connector, so check the tool list in your client before counting on a documented tool.

How writes behave

Each write takes effect when you approve the call in your client.
Gusto holds nothing as a draft.
The one two-step call Gusto documents is create_company. It runs first with confirmed: false to check the account email.

Payroll and pay

Tool	What happens
`update_payroll`	Changes hours, earnings, PTO, memos or payment methods on an unprocessed payroll, for up to 100 employees per call.
`run_payroll`	In Gusto's words, will "calculate and submit an existing unprocessed payroll". That is the step that pays people.
Payroll widget (Claude and ChatGPT versions)	Gusto doesn't document its behaviour, including any confirmation step.
`accept_reasonable_salary`	Accepts the latest reasonable-salary estimate as the owner's W-2 salary, so it changes compensation.

Other writes

record_time
manage_company_members (can send an onboarding invite)
manage_account (can resend the password-setup email)
save_company_onboarding_answer
acknowledge_scorp_recommendation
create_company
connect_bank_via_plaid (links the payroll funding account)
create_secure_gusto_session (opens a Gusto panel to sign a company form)
pay_ein_filing (a Stripe checkout link for a filing fee)
file_ein and file_scorp_election (prepare IRS forms)
create_reports and submit_feedback

Can

Read employees, compensation, departments and locations
Read contractors and contractor payments
Read payrolls and payroll blockers
Update and submit an unprocessed payroll
Record time; read time off and time records
Add or update one employee or contractor at a time, and resend onboarding invites or password-setup emails
Accept a suggested S-Corp owner salary as the owner's W-2 pay
Queue reports: payroll journal, cash requirements, contractor payments
Prepare EIN and S-Corp election filings

Cannot

Collect SSNs, ITINs, signatures or bank account and routing numbers in chat; those steps open secure Gusto panels or Plaid (per Gusto)
Complete an S-Corp election alone: the owner must still mail Form 2553 to the IRS (per Gusto)
Give tax, legal or HR advice; savings tools return estimates (per Gusto)
Look up workers' comp classes outside Washington and Wyoming (per Gusto)
Serve developers building on the Gusto API (Gusto points them to a separate MCP)

What access does it get?

Whatever data categories a Gusto global/full admin grants for one company during OAuth sign-in; Gusto doesn't publish the category or scope names.

Where	Scopes and permissions (as documented)	Admin requirement
Remote MCP server (any client)	OAuth 2.0 with PKCE; you select data types and the company, and access is limited to the categories you grant (per Gusto). Scope names not documented by the vendor; get_token_info shows active scopes.	A Gusto account with global/full admin permissions for the company (per Gusto's docs)
Claude connector (mcp.api.gusto.com/anthropic)	Same OAuth sign-in and category selection. Scope names not documented by the vendor.	Gusto global/full admin; Claude Team/Enterprise: an Owner adds connectors and can restrict them
ChatGPT app	Same OAuth sign-in; select a company if prompted. Scope names not documented by the vendor.	Gusto global/full admin; ChatGPT Business/Enterprise: an admin must allow the app

How do I connect it?

Add Gusto from the Claude connectors directory or ChatGPT, or point any remote-capable MCP client at https://mcp.api.gusto.com, then sign in as a Gusto admin and choose the data to share.

Preferred: open claude.com/connectors/gusto and click Add to Claude. The listing uses Gusto's Claude endpoint, https://mcp.api.gusto.com/anthropic, which Gusto's changelog ties to the payroll widget.
Or per Gusto's docs: click your avatar (bottom left) › Settings › Connectors › Add custom connector, name "Gusto", URL https://mcp.api.gusto.com, then Add. This generic URL may not show the payroll widget. Use one route only, so you don't end up with two Gusto entries.
If Gusto already shows "Configure", Gusto's steps say to click the ellipsis (...), choose Disconnect and confirm before you connect.
Click Connect, sign in to Gusto, choose the data types and company, then Authorize.
Keep each tool call on manual approval. Gusto's docs list Claude Pro or Max; on Team/Enterprise an Owner adds the connector first.

What should a finance team watch for?

This connector can submit payroll, so your client's per-call approval is the safeguard. Gusto asks you to confirm every tool call and to run the server on its own.

run_payroll submits a payroll and update_payroll can change payment methods. Gusto documents no approval step inside the tool, so keep automatic tool execution off and read each call before approving.
Gusto advises using the server in isolation, with no other MCP servers in the same client session, and only through trusted, well-established clients (Gusto names Claude, Gemini and Cursor). It also asks you to review closely any call that could send Gusto data to web search or third-party tools.
Prompt injection: payroll memos and employee fields are free text. An injected line could push the agent to change earnings or submit a payroll, so never auto-approve writes.
Least privilege: grant only the data categories you need at sign-in, then run get_token_info to confirm the scopes granted. To narrow or revoke access, disconnect (in Claude: Settings › Connectors › ... › Disconnect, per Gusto), which revokes the token, then reconnect. The connecting user must be a global/full admin.
Rate limits aren't published; Gusto returns HTTP 429 with Retry-After. Lists return 25 items per page by default, 100 at most.
Dates: per Gusto, list_payrolls filters on pay period dates by default. A payroll paid in one month can sit in the previous month's pay period, so say which date basis you want and tie totals to the payroll journal report.
Gusto says it logs tool names, sanitised parameters, timestamps, request IDs, OAuth and refresh tokens, company ID and usage metrics, and does not log full conversation history. It says tokens refresh automatically and are revoked on disconnect. Its no-training commitment covers only the AI providers Gusto contracts with, and it asks you to switch off training in your client; see Gusto's Privacy Notice.

How could finance teams and accounting firms use it?

The read tools suit payroll and headcount questions. The write tools suit preparing payroll changes and time entries that an admin confirms before Gusto processes them.

Inside a company

Ask for gross pay by department for the last pay period, then tie the totals to the payroll journal report.
List payroll blockers and upcoming pay periods ahead of a pay run.
Queue a payroll journal or cash requirements report to support the payroll accrual and cash forecast.
Prepare hours and earnings changes on an unprocessed payroll, then have an admin review every call before anything is submitted.

At an accounting firm

Pull a client's payroll journal report (CSV) and compare it with the payroll expense and liability accounts in the ledger. Gusto can't see the ledger, so bring a ledger export; Gusto advises against running another MCP server in the same session.
Review a client's contractor payments for the year ahead of year-end reporting.
Check headcount, terminations and compensation changes for a period before a client review meeting.
Plan for access: Gusto requires a global/full admin to connect, so agree with the client who holds that role.

Keep a person approving anything that changes payroll or employee records in Gusto, and tie AI-produced figures back to Gusto's reports before relying on them.

Want Gusto connected to Claude for your team?

We configure scoped connections and a review step before anything changes your books. Fixed fee.

Book a 30-minute setup call

Change log

Date	Change	Source
2026-09	create_reports and get_reports released (payroll journal, cash requirements, contractor payments); R&D credit tools and EIN filing tools added to onboarding	docs.gusto.com/app-integrations/docs/mcp
2026-07	update_payroll released	docs.gusto.com/app-integrations/docs/mcp
2026-02	Payroll widget for run_payroll live in the Claude variant; Gusto listed in the Claude connectors directory	claude.com/connectors/gusto
2026-01	ChatGPT app launched with the run_payroll widget	docs.gusto.com/app-integrations/docs/mcp
2025-08	Core MCP server live at mcp.api.gusto.com	docs.gusto.com/app-integrations/docs/mcp

FAQ

Is this official?

Yes. Gusto hosts the MCP server and documents it on docs.gusto.com. The Claude connector is listed as made by Gusto and Anthropic verified, and Gusto links its own ChatGPT app.

Is it free?

Gusto doesn't list a separate MCP charge. You need a Gusto global/full admin to connect; Gusto's docs list Claude Pro or Max and Cursor Pro+.

Does it change data in Gusto?

Yes. It can update and submit an unprocessed payroll, record time, add or update people and start filings. Each call runs once you approve it in your client, so keep approval on.

Is my data used to train models?

Gusto says its no-training commitment covers only its own AI providers and asks you to turn off training in your AI client. Check Gusto's and your AI provider's terms.

Can my accountant use it on my behalf?

Gusto doesn't document delegated access. Connecting requires a Gusto global/full admin for the company, so an accountant would need that role, which you may not want to grant.

Something wrong or out of date? Tell us and we'll email you when it's fixed.

Sources

Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.