Gusto MCP | OAuth 2.0 Gusto MCP connector for AI agents

Tools your hr agent reaches for on Gusto MCP, scoped per user.

CALL ANY TOOL

List employees and departments, retrieve payroll details, check pay periods, and view benefits plans.

gustomcp_get_company

Get Company

Retrieve the company profile including legal name, entity type, EIN, and status.

Parameters

Name

Type

Required

Description

_context

string

Optional

The original user question or request that prompted this tool call

gustomcp_get_compensation

Get Compensation

gustomcp_get_contractor

Get Contractor

gustomcp_get_contractor_payment

Get Contractor Payment

gustomcp_get_contractor_payment_group

Get Contractor Payment Group

gustomcp_get_department

Get Department

gustomcp_get_employee

Get Employee

gustomcp_get_employee_earnings_summary

Get Employee Earnings Summary

gustomcp_get_employee_home_address

Get Employee Home Address

gustomcp_get_employee_rehire

Get Employee Rehire

gustomcp_get_employee_work_address

Get Employee Work Address

gustomcp_get_job

Get Job

gustomcp_get_location

Get Location

gustomcp_get_pay_schedule

Get Pay Schedule

gustomcp_get_payroll

Get Payroll

gustomcp_get_time_sheet

Get Time Sheet

gustomcp_get_token_info

Get Token Info

gustomcp_list_contractor_payment_groups

List Contractor Payment Groups

gustomcp_list_contractor_payments

List Contractor Payments

gustomcp_list_contractors

List Contractors

gustomcp_list_custom_fields_schema

List Custom Fields Schema

gustomcp_list_departments

List Departments

gustomcp_list_earning_types

List Earning Types

gustomcp_list_employee_custom_fields

List Employee Custom Fields

gustomcp_list_employee_employment_history

List Employee Employment History

gustomcp_list_employee_home_addresses

List Employee Home Addresses

gustomcp_list_employee_jobs

List Employee Jobs

gustomcp_list_employee_terminations

List Employee Terminations

gustomcp_list_employee_work_addresses

List Employee Work Addresses

gustomcp_list_employees

List Employees

For more tools, view docs.

Build your Agent

Drop the toolkit in, point it at the user, and your hr agent can use Gusto MCP from the first run.

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["gustomcp"], toolNames: ["gusto_employees_list", "gusto_employee_get", "gusto_pay_periods_list"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: z.object({}).passthrough(),
  func: async (args) => {
    const { data } = await sk.tools.executeTool({
      toolName: t.tool.definition.name,
      identifier: "user_123",
      params: args,
    });
    return JSON.stringify(data);
  },
}));

const agent = createReactAgent({ llm, tools: lcTools });

import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["gustomcp"], toolNames: ["gusto_employees_list", "gusto_employee_get", "gusto_pay_periods_list"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["gustomcp"], toolNames: ["gusto_employees_list", "gusto_employee_get", "gusto_pay_periods_list"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/gustomcp",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start using Gusto MCP.

Employees & org

Copy the prompt

Copied

List all active employees in [department].

Copy the prompt

Copied

Get profile for [employee name].

Copy the prompt

Copied

How many employees are in [office location]?

Copy the prompt

Copied

Which employees were hired this month?

Payroll & benefits

Copy the prompt

Copied

What is the next pay period date?

Copy the prompt

Copied

List all benefits plans.

Copy the prompt

Copied

Get payroll summary for [pay period].

Copy the prompt

Copied

Which employees have pending status changes?

Reporting

Copy the prompt

Copied

Headcount by department.

Copy the prompt

Copied

New hires this quarter.

Copy the prompt

Copied

List employees with upcoming work anniversaries.

Copy the prompt

Copied

Which departments grew most this year?

SEE HOW AUTH WORKS

Users authorize Gusto MCP once. Their credentials stay vaulted, every call is checked, and every action is logged.

Authorize

Your user connects

Gusto MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Gusto MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Gusto MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Gusto MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

Same per-user auth pattern across other hr agents and MCP connectors. Working code, live demos, fork what fits.

ENGINEERING

Engineering standup agent

Aggregate GitHub and GitLab activity, link to Jira, and post a daily standup digest to Slack. No async updates.

ENGINEERING

DevOps assistant agent

Triage GitHub incidents, open Linear tickets, and notify the on-call channel in Slack with context already attached.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Gusto MCP today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Gusto MCP as the user or as a shared key?

As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Gusto MCP oauth 2.0 stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Gusto MCP?

Yes. Pass a tool name filter to listScopedTools so the HR agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Gusto MCP.

What happens when a user revokes Gusto MCP access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent access payroll data for all employees regardless of the user's HR role?

Only data the authorizing user's Gusto OAuth scope permits. Admin roles see full payroll; manager roles see their reports. Sensitive compensation data respects Gusto's native role-based access controls.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit