Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Query payroll, employee, contractor and timesheet data, and — for eligible customers — calculate and submit a payroll…
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Gusto MCP server connects a Gusto payroll account to Claude, ChatGPT, Slack and any MCP-compatible agent. It exposes 41 tools covering company records, employees, compensation, contractor payments, payroll history and timesheets — and, for customers Gusto has enabled, tools that calculate and submit a payroll run. Sign-in is OAuth and requires primary or global admin permissions in Gusto.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
calculate_payroll, submit_payroll and run_payroll.run_payroll shipping in February 2026. If you are relying on read-only behaviour, verify it against your account rather than that paragraph./anthropic endpoint returned HTTP 401 to an anonymous initialize on 2026-08-18, so names came from the directory snapshot and meanings from Gusto's documentation. No tool was called.update_payroll (July 2026), list_time_records and a deprecation of list_time_sheets (May 2026), and get_employee_earnings_summary (April 2026) — none of which appear in either the directory snapshot or Gusto's own 36-tool reference. Expect the live surface to differ from both.has_mcp_app: true for this connector, Gusto's changelog twice uses the word "widgetized" about run_payroll, and Gusto says that for sensitive actions it "blends conversational AI with the trusted Gusto interfaces" business owners know. We could not call resources/list — it requires a token — so we cannot describe what that widget shows.Retry-After header on exceedance, per Gusto's documentation.It can do both. Gusto's help centre states that connected platforms can read data and take action, and that one could request a payroll calculation or submit payroll for processing. The directory snapshot names calculate_payroll, submit_payroll and run_payroll. Gusto restricts payroll actions to a limited set of customers during early access.
Primary or global admin permissions in Gusto. Gusto lists that prerequisite for Claude, ChatGPT, Slack and every other AI platform, and its help centre says only payroll admins can connect and use these integrations. Gusto's MCP terms add that access is restricted to administrators with the appropriate permissions.
No separate fee. Gusto's help centre states there is no separate fee to connect Gusto to ChatGPT, Claude or Slack, but you need a platform account with the right feature enabled — Connectors for Claude, Apps for ChatGPT and Slack. Gusto's MCP terms reserve the right to charge service fees later.
Gusto lists company and location details, employee and contractor records, jobs, roles and compensation, department structure, payroll history and pay breakdowns, contractor payments, timesheets, pay schedules and payroll blockers. That includes employee home addresses and salaries. You pick which data categories to authorise during sign-in.
Gusto says you should. Its help centre instructs admins to tell team members that their personal information, payroll data and tax data may be shared with a third-party platform, noting some privacy laws including CCPA and CPRA require disclosure and some require consent. Gusto's terms make the employer solely responsible for obtaining consents.
Gusto runs client-specific routes. Its changelog records a Claude-specific endpoint going live in December 2025 and a widgetised run_payroll tool on that route in February 2026. We confirmed the bare host and an /openai path both answer initialize, while /mcp returns 404. Anthropic's directory lists the /anthropic route.
Gusto says no. Its documentation asks you to use the server in isolation and not connect other MCP servers to the same client session, warning that mixing servers can lead to your Gusto data being sent to another service. It also asks you to require manual confirmation for every tool call.
.md appended, updatedAt 2026-07-14). docs.gusto.com/robots.txt allows this path and carries no Content-Signal line. · retrieved 2026-08-18https://mcp.api.gusto.com/anthropic — initialize returnedauthorization_servers: ["https://mcp.api.gusto.com"] and publishes no scopes_supported field; the descriptor sits at the host root, not under /anthropic. · retrieved 2026-08-18payrolls:run and payrolls:write, PKCE S256, and a registration_endpoint. · retrieved 2026-08-18has_mcp_app (snapshot dated 2026-08-16) · retrieved 2026-08-16Connect Gusto once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.