Gusto MCP

Live

OAUTH 2.0

PAYROLL

Every employee, pay period, and benefits record your team manages lives in Gusto. Gusto MCP gives your agent authenticated access to payroll and HR data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Gusto MCP account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Gusto MCP
agent · Acme Q3
Run
How many active employees are in engineering and what is the upcoming pay period date?
S
gusto_employees_list
77ms
HR agent
42 active employees in Engineering. Next pay period: Nov 15 (semi-monthly). Last payroll processed Nov 1, $284K total. 3 employees with pending status changes before cutoff.
Sources: Engineering department, Gusto
gustomcpmcp
42 employees
18:29
Message Claude...

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.
gusto_employees_list
List employees
List employees with employment status and department filters.
Parameters
Name
Type
Required
Description
employment_status
string
Optional
Status: active, terminated, all
department_id
string
Optional
Department ID filter
gusto_employee_get
Get employee
gusto_pay_periods_list
List pay periods
gusto_payroll_get
Get payroll
gusto_benefits_list
List benefits
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.
1
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
2
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
3
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
4
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.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""gustomcp"": {
""url"": ""https://mcp.scalekit.com/gustomcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.gustomcp]
url = ""https://mcp.scalekit.com/gustomcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""gustomcp"": {
""url"": ""https://mcp.scalekit.com/gustomcp"",
""type"": ""http""
}
}
}