KeyPay MCP. Manage payroll, employees, and compliance data in natural language.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
KeyPay. Manage all your payroll, employee records, and pay runs using the Employment Hero Payroll API. This MCP server lets your agent check pay run statuses, list employee profiles, and pull payslips instantly.
It handles everything from leave tracking to complex deductions, letting you manage compliance data without logging into a separate HR system.
What your AI agents can do
Get business details
Retrieves specific operational details for a single business entity.
Get employee details
Pulls comprehensive information for one specific employee record.
Get pay run details
Gets detailed information for a single, specified pay run.
Use list_businesses and list_employees to pull lists of all entities and personnel associated with your payroll account.
Access list_pay_runs to see all pay cycles for a business, and then use list_pay_run_details to get deep details on a specific run.
Retrieve full employee data using get_employee_details and access their payslips with list_pay_slips.
Get a breakdown of money taken out or earned by calling list_pay_run_deductions or list_pay_run_earnings for any pay run.
List all pending or historical leave requests using list_leave_requests, and check which businesses exist using list_businesses.
Use get_business_details to confirm details for a specific business entity before running payroll queries.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
019d75c0get business details
Retrieves specific operational details for a single business entity.
019d75c0get employee details
Pulls comprehensive information for one specific employee record.
019d75c0get pay run details
Gets detailed information for a single, specified pay run.
019d75c0list businesses
Lists every business entity linked to your KeyPay account.
019d75c0list employees
Retrieves a list of employees associated with a specific business.
019d75c0list leave requests
Shows a list of leave requests (both pending and historical) for a business.
019d75c0list pay run deductions
Lists all specific deductions applied to a given pay run.
019d75c0list pay run earnings
Lists all earnings recorded for a specific pay run.
019d75c0list pay runs
Retrieves a list of all pay runs for a specified business.
019d75c0list pay slips
Gets a list of payslips issued for a specific employee.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with KeyPay, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Connect KeyPay to your AI agent. Your agent gets direct access to your core payroll and HR data. You'll manage businesses, employees, pay runs, and compliance records all through natural language commands.
Finding Businesses and Employees
Use list_businesses to pull a list of every business entity linked to your KeyPay account. You can confirm specific operational details for any single business using get_business_details. From there, pull a list of all employees associated with a business using list_employees. To get the full profile for one employee, call get_employee_details.
Tracking Pay Cycles and History
Your agent pulls a list of all pay runs for a specified business using list_pay_runs. You can then get deep details on any single pay run with list_pay_run_details. For a specific pay run, you can get a breakdown of all earnings using list_pay_run_earnings, or see every deduction applied with list_pay_run_deductions.
You can also pull a list of payslips issued to a specific employee using list_pay_slips.
Managing Leave and Organizational Structure
Check out all pending or historical leave requests for a business using list_leave_requests. You can confirm which businesses exist using list_businesses.
Analyzing Payroll Details
When you run payroll, you can verify payroll items and deductions. Use list_pay_run_deductions to list all specific deductions applied to a given pay run, and use list_pay_run_earnings to list all earnings recorded for that run.
How KeyPay MCP Works
- 1 Subscribe to the KeyPay server and enter your API Key and Region Domain.
- 2 Instruct your agent to call the necessary tool (e.g.,
list_businesses) and provide the required scope parameters. - 3 The agent executes the API call, returns the data payload, and allows your AI client to process the payroll information.
The bottom line is, your agent uses the KeyPay API to pull payroll data and structured HR records directly into your workflow.
Who Is KeyPay MCP For?
The Payroll Administrator who has to check pay run statuses across multiple companies. The HR Manager who needs to track leave requests and employee profiles quickly. Business Owners who need instant visibility into payroll costs and history without logging into a dedicated portal.
Checks pay run statuses, verifies employee details, and pulls detailed earnings reports for compliance checks.
Monitors pending leave requests, updates employee records, and queries payroll history for audits.
Gets instant visibility into total payroll costs across all registered businesses and tracks historical financial summaries.
What Changes When You Connect
- Check pay run status and earnings history instantly. Instead of navigating multiple internal screens, calling
list_pay_runsand thenlist_pay_run_earningspulls the full payroll picture immediately. - Get a full employee profile on demand.
get_employee_detailspulls all necessary employee metadata, eliminating the need to jump between the employee portal and the HR records system. - Audit deductions and earnings accurately. You can run
list_pay_run_deductionsandlist_pay_run_earningsfor any pay run to verify exactly how much was taken out or paid. - Track leave requests efficiently. Use
list_leave_requeststo see who took time off and if the request is pending, all in one query without manual searching. - Handle multiple company records.
list_businesseslets you see all entities in your account, allowing your agent to scope payroll tasks correctly from the start. - Retrieve payslips instantly.
list_pay_slipsgets the list of payslips for an employee, giving you immediate document access without file management.
Real-World Use Cases
Need to verify total payroll cost for an audit.
A Payroll Administrator needs to know the total earnings and deductions for the last pay cycle for Business X. They instruct their agent to first run list_pay_runs to find the correct ID, then call list_pay_run_earnings and list_pay_run_deductions using that ID. The agent returns a consolidated summary of the total cost.
Onboarding a new employee and checking their history.
An HR Manager needs to pull details for a new hire, John Doe, and check his employment status. They ask the agent to run list_businesses to scope the correct company, then call list_employees to find John's ID, and finally get_employee_details to pull his full profile.
Checking compliance for a specific pay period.
A Payroll Administrator wants to confirm if specific tax deductions were applied correctly for the last pay run. They use list_pay_runs to identify the pay run ID, and then run list_pay_run_deductions to inspect every deduction line, confirming compliance.
Need a summary of leave and pay status for a department.
A Business Owner wants a quick status report. They ask the agent to run list_leave_requests to see who is out, and simultaneously run list_pay_runs to see when the last pay cycle closed for the business.
The Tradeoffs
Guessing the correct Business ID
The user manually enters a business ID into the prompt and the agent fails because the ID is wrong or outdated. The user has to restart the query, wasting time.
→
First, call list_businesses to get the definitive list of all available business IDs. Then, scope all subsequent calls (like list_employees or list_pay_runs) using the confirmed ID.
Trying to get all employee data in one shot
The user asks the agent, 'Give me all employee data.' The agent hits a rate limit or returns an incomplete, unpaginated list, forcing the user to guess which subset was missed.
→
Use list_employees to get the complete, paginated list of employee IDs first. Then, loop through the resulting IDs and call get_employee_details for each one to build a complete record.
Missing the payslip record
The user checks pay runs and sees earnings, but doesn't know how to get the actual document. They end up searching through email archives.
→
After identifying the employee and the relevant period, use list_pay_slips to get a list of payslips, which provides immediate access to the required document.
When It Fits, When It Doesn't
Use this if you need to pull structured, verifiable HR and payroll data for multiple entities or for auditing purposes. If your goal is simply to read a document (like a payslip), use list_pay_slips. If you need to know who works there, start with list_businesses and then list_employees. Don't use this if you need to make changes (like updating an employee's address); this server is for reading and reporting data only. If you only need one piece of information (e.g., just the total count of businesses), list_businesses is enough, but if you need the data for a specific business, you'll need get_business_details first.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by KeyPay. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually compiling a payroll summary takes forever.
Right now, compiling a payroll summary is a nightmare. You open the HR portal, check the employee list. Then you open the payroll system to check pay run statuses. You switch tabs to check leave requests, and then you open a spreadsheet to calculate total deductions. It's a mess of logins, clicks, and copy-pasting data points across three different applications.
With the KeyPay MCP Server, your agent handles the coordination. You ask, 'What were the total costs for the last pay cycle?' and the agent runs the necessary tools (`list_pay_runs`, `list_pay_run_earnings`, etc.) and returns a single, consolidated answer. You get the data, not the headache.
KeyPay MCP Server: Get instant access to employee and pay data.
Before this, checking an employee's full record—including their history, leave balance, and pay details—meant logging into multiple systems. You'd check the employee directory, then check the leave management system, and finally check the payroll platform. Every single check was a manual step.
Now, your agent runs `get_employee_details` and `list_leave_requests` in sequence. You get the complete picture—status, history, pay data—in one conversational turn. It's just that simple.
Common Questions About KeyPay MCP
How do I use the KeyPay MCP Server to find all my companies? +
You run list_businesses. This tool pulls a list of every business entity associated with your KeyPay account. It gives you the starting scope for any other query you run.
Can I use KeyPay MCP Server to see deductions for a pay run? +
Yes, use list_pay_run_deductions. This tool requires a specific pay run ID and will list every deduction applied during that cycle.
What tool do I use to get an employee's payslip? +
Use list_pay_slips. This tool requires an employee ID and will retrieve a list of payslips for that employee, giving you document access.
What if I need to check pay runs for a business, but don't know the ID? +
First, run list_businesses to confirm the correct business ID. Then, use list_pay_runs with that ID to get all available pay run IDs.
How do I use the `list_employees` tool to find all employees for a specific business? +
You use list_employees and provide the business ID. This command returns a full list of employees associated with that business ID.
What tool do I use to check the status of all pay runs for a business? +
Use list_pay_runs. This tool fetches all pay runs for a business, letting you see their status and dates at a glance.
If I need to find a specific employee's details, which tool should I use? +
Use get_employee_details. You just need the employee's ID and the business ID to get their full profile.
How do I use the `get_business_details` tool to verify a business's setup? +
Run get_business_details with the business ID. The response provides core details, helping you confirm the business's current setup.
In which regions is the KeyPay API available? +
KeyPay supports multiple regions including Australia, UK, New Zealand, Singapore, and Malaysia. Make sure to provide the correct region domain during setup.
Can I see my employee's payslips using this agent? +
Yes, the list_pay_slips tool allows you to retrieve a list of issued payslips for a specific employee within a business.
Is it possible to track leave requests? +
Absolutely. Use the list_leave_requests tool to fetch all historical and pending leave requests for any of your registered businesses.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Factorial
Modernize HR operations with time-off management, payroll processing, and performance reviews that employees actually enjoy using.
OnPay
Payroll and HR management — manage employees, transactions, and schedules via OnPay.
LearnUpon
Manage users, courses, and enrollments via the LearnUpon LMS API.
You might also like
Factorial
Manage HR operations via Factorial — list employees and teams, track leave requests, monitor shifts and payslips, and handle company documents directly from any AI agent.
Proforms
Online form builder and data collection.
EMT Madrid (Open Data)
Access real-time Madrid public transport data: bus arrivals, BiciMAD bike status, and route planning via EMT Open Data.