
HR and payroll data for AI agents. Every answer cites its source.
HyperSync MCP connects Claude, Cursor, Windsurf and VS Code to normalized employee and payroll data across 76 HRIS, payroll, ERP and SSO integrations. Read-only, permission-scoped and audited.




The Problem
Your agent is ready. Your employee data isn’t.
Every employer runs a different HRIS. Every HRIS names, shapes and stores pay data differently. Agents built on raw integrations inherit every inconsistency — and report it with confidence.
Salary: $84,000/mo
Wrong time base
Annual and period figures sit side by side in raw payloads. Agents mix them and report raises or pay cuts that never happened.
Routing no: 0412
Wrong field
A field called BankCode is a routing number in one system and a branch code in another. Mapping it straight across is a silent error.
Status: Active (as of ?)
No provenance
Raw API responses rarely say how fresh the data is. Agents present last month’s record as today’s.
Building and maintaining these integrations yourself is a roadmap, not a sprint.
How it works
One server. One schema. Every HRIS.
Why a synced store, not live API calls?
Live calls on every tool invocation are slow, inconsistent across providers and fragile under rate limits. A synced store gives agents predictable latency and one response shape, and every response tells you exactly how fresh it is.
1
Sync
HyperSync connects to each employer’s HRIS and payroll system and syncs records on a schedule.
2
Normalize
Every provider’s fields map into the Tartan Unified Schema. grossPay means gross pay for the stated period, whichever system it came from.
3
Serve
HyperSync MCP exposes that data as tools any MCP client can call, over Streamable HTTP.
Live demo
Watch an agent verify income in four calls.
The same flow your analysts run today, without the document chase.
1
Find the connector
Which HRIS connectors are active for Acme Corp?
hypersync_list_connectors
2
Check freshness
(agent, unprompted) Checking sync status before using this data.
3
Pull pay details
Get October 2026 pay details for EMP-1042.
4
Cite the source
Monthly gross pay was $6,400; net $4,756. Source: [provider], synced 2h ago.
Every HyperSync MCP response carries the provider, connector, sync run and last-synced time. Your agent cites it. Your analyst verifies it. Your auditor finds it.
Try it in the sandbox →
Use cases
Built for teams that run on employee data.
Storyboard: four tabs across the top, remembered via UTM (?for=lending). Shown here as four cards — tabs can be added as a component.
Lending and verification
Verify income and employment at the source.
Read pay directly from the employer’s payroll record instead of a pay stub upload. Debt-to-income starts from structured numbers, not OCR output. Analysts review exceptions instead of transcribing documents.
Compare EMP-1042’s October net pay with the stated income on application #88231.
AI and agent builders
Ship HR data features without building HR integrations.
One MCP server and one schema across 76 integrations. Typed fields, consistent envelopes, explicit freshness. Point your agent at it and move on to the product.
List active connectors for this tenant and tell me which support payroll reads.
Benefits, Insurance and HRMS
Price, enrol and advance against real pay data.
Confirm compensation behind salary-multiple coverage. Check existing payroll deductions before recommending a contribution.
What is EMP-2210’s annual compensation, and which insurance deductions already run through payroll?
HR and people operations
Answer payroll questions in seconds, with the breakdown.
“Why is my net pay lower this month?” has a real answer when deductions arrive as separate, typed components.
Break down the difference between EMP-0318’s September and October net pay.
Tools
Tools your agent can call today.
hypersync_list_connectors
Lists HRIS connectors for your tenant. Start here.
Live
hypersync_get_connector
Approval state, sync config and domains for one connector
Live
hypersync_get_connector_capabilities
Which actions a connector supports
Live
hypersync_get_sync_status
Freshness and last successful sync
Live
hypersync_get_employee_salary_details
Earnings, bonuses, deductions, annual compensation and net pay, by date range
Live
hypersync_search_employee_directory
Filter by department, title, status, hire date
Next
hypersync_list_employee_documents
Pay stubs, tax forms, contracts
Next
hypersync_explain_mapping
Which source field maps to a schema field, and why a field is empty
Next
Governed write tools
Validated, confirmation-gated profile, address, bank and employment updates
Next
Full tool reference in docs →
Governance
Built to clear security review, not stall in it.
Employee and payroll data is some of the most sensitive data you handle. HyperSync MCP is designed so the model never gets to decide what it is allowed to do.
Read-only today
The current release reads data. It cannot change an employee record.
Pay data has its own scope
Baseline access covers connectors and employee data. Pay details need a separate salary.read permission, checked at the gateway and again inside the tool.
Acts as the user
Every call carries the caller’s own OAuth token, verified for signature, issuer, audience and expiry before any tool runs.
No stored credentials
The gateway forwards the caller’s token downstream and holds no long-lived credential. There is nothing to steal and replay.
Provenance on every answer
Provider, connector, sync run and last-synced time come back with every response.
Every call logged
Tool invocations are audit-logged by caller, tool and time.
Token verified
→
Scope checked
→
Synced store queried
→
Response + source
→
Call logged
SOC 2 · ISO 27001 · ISO 27701
Download the security brief →
Quickstart
From config to first call in ten minutes.
1
Get sandbox access
A synthetic tenant with realistic employees, connectors and payroll. No HRIS needed.
2
Add the server to your client
Paste the config. Authenticate with OAuth.
3
Ask your first question
Start with “Which connectors are active?” and follow the flow.
Build vs. HyperSync MCP
You could build this. Here’s what it costs.
Build it yourself
HyperSync MCP
Integrations
One connector per HRIS, maintained forever
76 HRIS, payroll, ERP and SSO integrations behind one server
Data model
Your own mapping per provider, per field
One schema; ambiguous fields mapped and flagged
Freshness
Build sync, retries and staleness tracking
Sync status tool and last_synced_at on every response
Permissions
Design scopes, roles and enforcement
Separate pay scope, checked twice
Auth
Build OAuth for every client
OAuth 2.1 resource server, standard discovery
Audit
Build logging and retention
Every tool call logged
Spend your roadmap on the agent, not the plumbing.
Coming next
Agents that can update the HRIS - safely.
Reading is half the workflow. The next release adds controlled writes for profile, address, bank and employment updates, built so a wrong write cannot slip through.
✓
Validated on the server.
Every change passes a validation tool inside HyperSync, never inside the model.
✓
Dry run by default.
See exactly what will be sent to the provider before anything changes.
✓
Confirmation required.
High-impact writes need a confirmation token from the validation step.
✓
Capability-checked.
Actions a connector doesn’t support are blocked before they’re attempted.
✓
Fully audited.
Old value, new value, user, connector and provider response are logged on every write.
An MCP server that gives AI clients such as Claude, Cursor, Windsurf and VS Code access to normalized employee and payroll data from the HRIS and payroll systems connected through HyperSync.
Any system connected through HyperSync's 76 integrations, including [confirmed US providers]. Call hypersync_list_connectors to see what is live for your tenant.
Not today. The current release is read-only. Governed writes, with server-side validation, dry runs and confirmation tokens, are coming next.
No. It reads from HyperSync's synced, normalized store for speed and consistency. Every response tells you when that data was last synced.
Pay details sit behind a separate permission scope, checked at the gateway and inside the tool. Every call is authenticated as the user and logged.
The gateway is an OAuth 2.1 resource server and publishes standard protected-resource metadata, so compliant clients can discover how to sign in.
Yes. The sandbox tenant has synthetic employees, connectors and payroll data.

Give your agents employee data they can cite.
Buyers
See it on your workflow
A 30-minute walkthrough on your verification or benefits flow.
Book a walkthrough














