Gusto

Gusto

This connector reads one Gusto company through the Gusto API for app integrations (https://api.gusto.com, or https://api.gusto-demo.com for demo companies), version 2026-06-15: the company with its locations and admins, employees (with jobs, compensations and employment history), contractors, departments, pay schedules and pay periods, payrolls and contractor payments, time off policies and requests, earning types and company benefits. It runs as the Gusto admin who authorized it, on the one company chosen at sign-in.

Payroll is read-only here. No tool prepares, calculates, submits or cancels a payroll, and none creates or funds a contractor payment, an employee, a compensation or a termination. The only writes are gusto_create_department and gusto_update_department (the second is installed switched off).

Setup (one-time, about 15 minutes)

1. Create a free account on the Gusto Developer Portal at https://dev.gusto.com and create an application there. A new application starts in the demo environment, where everything runs against test companies.
2. In the application's settings add the redirect URI https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP URL>/api/mcp-oauth/callback when you host AnythingMCP yourself. Gusto accepts no wildcards. Demo redirect URIs can be edited in the portal; for a production application Gusto changes them on request ([email protected]).
3. Copy the application's Client ID and Secret into GUSTO_CLIENT_ID and GUSTO_CLIENT_SECRET.
4. Set GUSTO_API_URL to https://api.gusto-demo.com for a demo application or https://api.gusto.com once Gusto has approved the application for production. The keys only work on their own environment.
5. For a test, create a demo company in the Developer Portal; it comes with sample employees, contractors and payrolls.
6. Install, click Authorize with Provider and sign in to Gusto as a primary or full-access admin. Gusto asks which company to connect: one authorization covers exactly one company. Install the connector again for a second company.
7. Run gusto_get_token_info. resource.uuid is the company UUID that every company tool takes as company_uuid; scope lists what the application may read.

Scopes are not requested at sign-in: Gusto assigns them to the application (in the demo environment broadly, in production after its review). A call outside them answers 403. Pay rates and compensations (rate, payment_unit, compensations) appear only with the compensations:read scope; benefits with health information need the :phi scopes.

API version: every call sends X-Gusto-API-Version: 2026-06-15. Gusto answers 406 when that is older than the application's minimum API version (shown in the Developer Portal) or newer than the versions it knows.

Tokens: access tokens last two hours and are renewed automatically. Gusto issues a new refresh token on every renewal and the old one stops working; AnythingMCP stores each new one. Do not use the same authorization in another tool at the same time, or one of the two ends up with a used refresh token and has to authorize again.

Workflow

• People: gusto_list_employees (filter by terminated, onboarded, search_term; jobs are included in each employee), then gusto_get_employee, gusto_get_employment_history, gusto_list_job_compensations with a job uuid from jobs[].
• Contractors: gusto_list_contractors, gusto_get_contractor, gusto_list_contractor_payments (needs start_date and end_date).
• Payroll: gusto_list_pay_schedules, gusto_list_pay_periods, gusto_list_payrolls (by default processed regular payrolls of the last six months; at most one year between start_date and end_date), then gusto_get_payroll with include = totals,taxes,deductions,benefits for the breakdown per employee.
• Organisation: gusto_get_company, gusto_list_locations, gusto_list_company_admins, gusto_list_departments, gusto_list_earning_types, gusto_list_company_benefits.
• Time off: gusto_list_time_off_policies, gusto_get_time_off_policy (balances per employee), gusto_list_time_off_requests.

Reading the data: money is a decimal string ("1234.56") and hours have three decimals. Dates are YYYY-MM-DD. Ids are UUIDs. Lists with page and per return the totals in the x-total-count and x-total-pages headers; without them Gusto returns every record, except payrolls, which always come in pages (this connector asks for 100, the maximum).

Confirm first: gusto_create_department and gusto_update_department change what every admin sees in Gusto. Department updates need the current version from gusto_get_department; a stale version answers 409.

Common errors

• 401: the authorization was revoked or not renewed; click Authorize with Provider again.
• 403: the application lacks the scope for this call, or the token belongs to another company than company_uuid.
• 404: wrong UUID, or a resource of another company.
• 406: X-Gusto-API-Version is outside the versions your application allows.
• 429: more than 200 requests in a minute for this authorization; wait a minute.

Out of scope here: running, calculating or submitting payrolls, paying contractors, onboarding or terminating people, changing pay, benefits enrollment, tax forms and documents, webhooks. Gusto Embedded (partner-managed companies) is a different product and is not covered.