Payroll / HR
Gusto MCP (direct)
Published by Gusto
First-party live payroll and people data, separate from the Zapier route. Gusto's published guidance requires an isolated client session without other MCP servers and manual confirmation for every tool. Payroll is supporting evidence, not complete earnings before owner compensation. Documented offering; connection not tested by ValuationMCP.
Remote
OAuth
Official
What this server supplies
Supporting context only. No valuation checklist fields are mapped to this server; the source limitations above still apply.
What you approve
- 1.Use a trusted client in an isolated session with no other MCP servers, as Gusto's integration guidance requires.
- 2.Require manual confirmation for every tool call and decline payroll, onboarding and other writes.
How your agent connects it
- 1.Use Gusto's published connector setup for your supported assistant; do not connect ValuationMCP in the same session.
- 2.Review payroll and compensation evidence in isolation. Resolve the vendor's isolation restriction before using a combined MCP valuation workflow.
Figures, not records
Your agent reads Gusto MCP (direct) directly and passes only the figures the valuation needs. Those numbers are stored on your practice record alongside their provenance and the calculated outputs. The statements, exports, position data and CRM records behind them stay in your platforms. In your AI assistant, your own connectors do the reading, and ValuationMCP never receives their credentials. If you connect a system in the web workbench, its credentials are stored encrypted, used only for read-only pulls you start, and deleted when you disconnect. See the Privacy Policy.
Server details, tier and auth mode reviewed against the publisher's documentation.

