Darwinbox

Darwinbox MCP Server

Knit's Darwinbox MCP Server gives your AI agents instant, code-free access to every Darwinbox API endpoint-read, write, and automate without OAuth headaches or custom endpoints.

Building Integrations Together·4.9 out of 5 stars4.9/5 on G2·GoogleGoogle for Startups Accelerator
prismforceHackerearthIsotopes AIInfojobsPayoneerOutsolveSkuadPayworksItiliteOnsurityRazorpayXMultiplierPeoplestrongScrutCeipal

Key Features

All the power of AI-ready tools — serverless hosting, mix-and-match APIs, live updates, semantic search, and built-in auth — in a single, plug-and-play platform.

Serverless by Default

Spin up MCP Servers with zero infrastructure — Knit scales, patches, and monitors everything for you.

Mix-and-Match Tool Bundles

Deploy only the API tools you need from any app in a single lightweight server — no bloat, no duplication.

Plug-In Your Own APIs

Expose custom endpoints as AI-ready tools alongside Knit's catalog, unifying proprietary logic and third-party apps in one place.

Semantic Tool Search

Natural-language search surfaces the right tools for each use case, shrinking token costs and boosting LLM accuracy.

Hot-Swap Tools at Runtime

Add or remove tools without downtime; your agents see new capabilities instantly — no server restarts required.

Auth Handled for You

OAuth, SAML, service accounts — Knit manages credentials and refreshes so your team never wrestles with tokens.

See It In Action

Watch an agent automate workflows — all with Knit's plug-and-play MCP Servers.

Actions Available via Darwinbox MCP Server

Every action below is real and already live — not a roadmap item. Browse the full API reference →

Create Employee

The Create Employee API allows you to create a new employee record in the system. It requires a POST request to the endpoint with necessary headers and a JSON body containing employee details such as first name, last name, employment details, work email, and more. The employment object must include a positionId and designation. The API supports various HR applications, each with specific requirements and unsupported fields. The response includes a success flag and the employeeId of the newly created employee. In case of an error, a descriptive error message is returned.

Enroll Employee Deductions

The Enroll Employee Deductions API allows for enrolling an employee in a deduction plan. It requires the employee ID as a mandatory field. Other optional fields include deduction ID, deduction code, employee and employer contributions, start date, and metadata. The API supports various apps like ADP Run, Paycor, Paychex, Paylocity, PrismHR, Avionte, and ADP Workforce Now. The response indicates success or failure, with an optional error message in case of failure.

List HR Departments

The List HR Departments API retrieves a list of departments from the HR system. It supports multiple applications such as Workday, SAP SuccessFactors, GreytHR, and more. The API requires an 'accept' header specifying 'application/json'. It has an optional query parameter 'originData' which defaults to false. The response includes a success flag and a data object containing an array of department objects, each with an id, name, description, parentId, and companyId. In case of an error, the response will include a success flag set to false and an error message.

Get Employee Leave Balance

This API endpoint retrieves the leave balance for a specified employee for the current year. It requires the 'employeeId' as a query parameter and optionally accepts 'originData' to include the origin API response. The response includes a list of leave balances, detailing the type of leave, unit, available balance, and used balance. Supported applications include Darwinbox, GreytHR, Zoho People, Workday, Sage, ADP Workforce Now, Personio, BambooHR, Paychex, Remote, Deel, Paycor, Ceredian Dayforce, Rippling, UKG Pro, Keka HR, and UKG Ready.

Update Employee Compensation

The Update Employee Compensation API allows updating the compensation details of an employee. It requires the employee ID and the effective date of the update. The request body can include fixed, variable, and stock compensation elements, each with specific properties such as type, planId, amount, percentage, currency, payPeriod, and frequency. The API supports various applications like Workday, Hibob, BambooHR, and others, each with specific rules for updating compensation. The response indicates success or failure, with an optional error message in case of failure.

Add HR Attendance Record

The Add HR Attendance Record API allows you to add an attendance record for an employee. It requires the employee ID as a mandatory field, and optionally accepts check-in and check-out date-time values, along with metadata that can include fields like break_duration or remarks. The API supports various apps like Darwinbox, HROne, and Lucca HR, each with specific metadata fields. The response indicates success or failure of the operation, with a success flag and optional error message.

Get Employee Field Values

The Get Employee Field Values API retrieves the values for specified employee fields such as employmentType and employmentStatus. It supports various HR applications like BambooHR, Darwinbox, GreytHR, Keka HR, Zoho People, Hibob, Workday, Paycom, Paycor, Paychex, HR One, Alexis HR, and UKG Ready. The API requires a query parameter 'fieldType' to specify the type of field to retrieve. The response includes a success flag and a list of fields with their IDs and labels. In case of an error, an error message is provided.

Create HR Deduction

The Create HR Deduction API allows users to create a new deduction in the HR system. The API requires a POST request to the endpoint with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include the deduction's name, type, frequency, description, and any additional metadata. Upon success, the API returns a response with a 'success' flag and the 'deductionId' of the newly created deduction. In case of an error, the response includes a 'success' flag set to false and an error message.

Get Payroll Statement for an Employee

This API endpoint retrieves the payroll statement for a specified employee for a given month or date range. The request requires the 'employeeId' as a mandatory query parameter. You can specify the time range using either the 'month' parameter in 'yyyy-mm' format or 'startDate' and 'endDate' parameters. However, some apps like Darwinbox, GreytHR, and RazorpayX Payroll require the 'month' parameter and do not support 'startDate' and 'endDate'. The response includes details such as gross pay, net pay, processed date, pay date, earnings, contributions, and deductions. The API supports various HR systems like Keka HR, Zoho People, Workday, and more.

Update Employee Details

The Update Employee Details API allows updating various details of an employee such as personal and work email addresses, present and work addresses, and employment details. The API supports multiple HR applications, each with specific field support limitations. The request requires an employeeId and can include optional fields like firstName, lastName, workEmail, personalEmails, presentAddress, workAddress, employment, and metadata. The response indicates success or failure, with an optional error message in case of failure.

Update Employee Deductions

The Update Employee Deductions API allows updating the deduction details for an employee. It requires the employeeId as a mandatory field in the request body, along with optional fields such as employeeDeductionId, deductionId, employeeContribution, employerContribution, and metadata. The API supports applications like ADP Run, Paycor, Paychex, Paylocity, and ADP Workforce Now. The response indicates success or failure of the operation, with a success flag and optional error message.

Get Compensation Plans

The Get Compensation Plans API retrieves compensation plans including fixed, variable, and stock components. It supports various applications such as Workday, Hibob, Paycor, SAP Successfactors, Paychex, Quickbooks Payroll, Lucca HR, and PrismHR. The API requires an 'accept' header with 'application/json' and optionally accepts a 'originData' query parameter to include origin data. The response includes detailed compensation data with fixed, variable, and stock plans, or an error message if the request fails.

Get HR Document Categories

The Get HR Document Categories API retrieves a list of document categories available in the HR system. It supports various applications such as Workday, Sage, Hibob, Personio, Zoho People, SAP Successfactors, Keka, and Avionte. The API requires an 'accept' header specifying 'application/json'. It has an optional query parameter 'originData' which is a boolean flag to include origin data, defaulting to false. The response includes a 'success' flag and a 'data' object containing an array of categories, each with an 'id' and 'name'. In case of an error, an 'error' object with a descriptive message is returned.

Get Leave Types

The Get Leave Types API retrieves a list of leave types supported by various HR applications. The request is made using the GET method to the endpoint https://api.getknit.dev/v1.0/hr.leave.types. It accepts a query parameter 'originData' which is a boolean flag to include origin data, defaulting to false. The request header must include 'accept: application/json'. The response includes a success flag and a data object containing an array of leave types, each with an id, name, and type. In case of an error, the response will include a success flag set to false and an error message.

Terminate Employee

The Terminate Employee API allows you to terminate an employee by providing their employee ID, termination date, and termination reason. The API requires the 'accept' and 'content-type' headers to be set to 'application/json'. The request body must include 'employeeId', 'terminationDate', and 'terminationReason'. Optionally, 'metadata' can be provided for additional information. The response will indicate success or failure, with an error message if applicable. Supported apps may have specific requirements for the 'terminationReason' and 'metadata' fields.

Get Employee Attendance

This API retrieves a list of attendance records for a specified employee within a given month. The request requires the 'employeeId' and 'month' as query parameters. An optional 'originData' parameter can be included to return the origin API response. The response includes details such as date, shift start and end times, total hours, break hours, effective hours, first in and last out times, and attendance status. The API is supported by various HR applications including Darwinbox, Keka HR, GreytHR, and others.

Unenroll Employee Deductions

The Unenroll Employee Deductions API allows supported applications to unenroll an employee from specific deductions. The API requires a POST request to the endpoint with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include the 'employeeId' as a required field, and optionally 'employeeDeductionId', 'deductionId', 'deductionCode', and 'metadata'. The response will indicate success with a boolean and may include additional data or an error message if the operation fails.

Create Employee Leave Request

This API endpoint allows the creation of a leave request for an employee. It requires the employee ID, leave type ID, start and end date-time, unit of leave (DAYS or HOURS), and the amount of leave. The request body must be in JSON format. On success, it returns a success status and the leave request ID. If the request fails, it returns an error message.

List HR Deductions

The List HR Deductions API allows users to retrieve a list of HR deductions. It supports various applications such as SAP SuccessFactors, ADP Run, Paycor, Paychex, Workday, Paylocity, UKG Ready, and PrismHR. The API uses the GET method and requires the 'accept' header to be set to 'application/json'. It has an optional query parameter 'originData' which is a boolean flag to include origin data. The response can be a list of deductions with details such as deductionId, deductionCode, type, description, frequency, startDate, and isTax. In case of an error, the response will include a success flag and an error message.

Update HR Deductions

The Update HR Deductions API allows users to update details of HR deductions. It requires a POST request to the endpoint 'https://api.getknit.dev/v1.0/hr.deductions.update'. The request must include headers specifying 'accept' and 'content-type' as 'application/json'. The body of the request must include the 'deductionId' as a required field, and optionally 'frequency', 'description', and 'metadata'. The response will indicate success with a boolean 'success' field and may include additional data or error messages.

List HR Companies

The List HR Companies API endpoint allows users to retrieve a list of HR companies. It supports various applications such as Darwinbox, Rippling, Workline, and more. The API uses the GET method and requires an 'accept' header with the value 'application/json'. It also accepts an optional query parameter 'originData' which is a boolean flag to include origin data. The response includes a success flag and a data object containing an array of companies, each with details like companyId, companyName, and address information. In case of an error, an error message is provided.

Get Employee Positions and Work Shifts

This API endpoint retrieves the list of employee positions and work shifts. It supports various HR applications such as Workday, Sage, Hibob, and more. The request is made using the GET method to the URL https://api.getknit.dev/v1.0/hr.employees.positions. The request requires an 'accept' header with the value 'application/json'. An optional query parameter 'originData' can be included to specify if origin data should be included in the response. The response includes a success flag, a list of positions with their IDs, designations, and departments, and a list of work shifts with their IDs and names. In case of an error, the response will include an error message.

Get Employee Leave Requests

This API retrieves a list of leave requests for a specified employee within a given date range. The request requires the 'employeeId' as a mandatory query parameter. You can specify the time range using either the 'month' parameter in yyyy-mm format or 'startDate' and 'endDate' parameters. The response includes details such as leave request ID, start and end dates, status, leave type, and whether the leave is paid. The API supports various HR applications such as Darwinbox, Keka HR, GreytHR, and others.

Upload Employee Document

The Upload Employee Document API allows users to upload documents for employees. The API requires the employee ID and file name as mandatory fields. The document can be uploaded by providing either the base64 encoded content or a URL to the file. Additional optional fields include content type, category, comment, and metadata. The response includes a success flag and the document ID if successful, or an error message and type if the request fails. The category field is mandatory for some applications like Darwinbox and Zoho People.

Get Termination Reasons

The Get Termination Reasons API retrieves a list of termination reasons supported by various apps such as Workday, Hibob, BambooHR, Remote, 7shifts, and UKG Ready. The API requires an 'accept' header specifying 'application/json'. It supports an optional query parameter 'originData' which defaults to false. The response includes a success flag and a data object containing an array of termination reasons, each with an 'id' and 'name'. In case of an error, an error message is provided.

Missing an action?

Our AI Agent builds it instantly.

Try Now

Knit vs. building a standalone Darwinbox MCP Server

Building it yourself

  • A custom MCP server for Darwinbox, hosted and maintained in-house
  • Handle Darwinbox's OAuth, rate limits, and pagination yourself
  • Re-test and patch every time Darwinbox changes their API
  • No tool search — every tool sits in your agent's context at once
  • Engineering time spent on plumbing, not your product
  • Weeks of dev time before you ship

With Knit

  • Darwinbox MCP Server already built, hosted, and maintained
  • Knit handles Darwinbox's OAuth, storage, and refresh for you
  • Knit absorbs Darwinbox's API changes — nothing breaks on your end
  • Semantic tool search keeps agent context lean
  • Your team ships your product, not integration plumbing
  • Live in minutes, not weeks

Enterprise-grade security

SOC 2 certified GDPR compliant ISO 27001 certified
Visit our Security Center Review the DPA

Customer Stories

See how leading technology firms are scaling their operations

Amazing Product With Exceptional Support from the team. By using Knit we managed to speed up our development by orders of magnitude.
H
Huynh H
Developer, Multiplier
A brilliant tool to let you seamlessly integrate with many different systems. It is very easy to integrate with and customer support is next level.
J
Jayesh
Co-Founder, Scrut
Seamless integration experience. Well-documented, self-explanatory APIs, and excellent service and support.
P
Poorvi
Product Manager, Onsurity
Easy to integrate. Knit's dashboard is intuitive for setting up and testing integrations, and the sandbox is extremely useful during development.
A
Aditya
Product Lead, RazorpayXPayroll
Knit shipped a brand-new Timesheet API in a week and handed us a ready-to-use NetSuite sandbox. That velocity is priceless when you're running payroll in 40+ countries.
R
Rohit Singh
GM, Payoneer Workforce Management

#1 in Ease of Integrations

4.9 out of 5 stars

4.9 out of 5 stars on G2

G2 Leader, Spring 2026G2 Fastest Implementation, Spring 2026G2 High Performer, Spring 2026G2 Best Est. ROI, Spring 2026
FAQ

Common questions about the Darwinbox MCP Server

Does Knit have an MCP Server for Darwinbox out of the box?

Yes — the Darwinbox MCP Server is live and already built, not a roadmap item. It exposes Darwinbox's real actions as AI-ready tools your agent can call directly.

Does the Darwinbox MCP Server support both reading and writing data?

Yes. Its actions cover both reads and writes, so your agent can pull data from Darwinbox and push updates back to it, not just query it.

How does authentication work for the Darwinbox MCP Server?

Knit manages Darwinbox's OAuth, credential storage, and refresh for you — there's no auth to configure yourself before your agent can start calling tools.

What happens if Darwinbox changes their API?

Knit absorbs it. We maintain and update the Darwinbox connector on our end, so the MCP Server keeps working without you tracking Darwinbox's changelog.

Do you store Darwinbox data or customer PII?

No. Knit acts as a stateless passthrough — data is processed on our application server and returned directly to your agent, without being stored on Knit's servers.

What is the pricing model, and is there a free trial?

You choose the model that fits your business — pricing based on integrated accounts, or based on API call volume. Every plan includes a 30-day free trial before billing starts.

Can I use this as an LLM tool for function calling?

Yes — this MCP server exposes Darwinbox's actions as tools your AI agent can call directly, the same underlying capability previously offered as a standalone LLM Tool integration. MCP is the protocol; the tool-calling access is the same.

Does this work with Claude, GPT, and other LLMs?

Yes — any MCP-compatible client or agent framework can connect to this server and call its exposed actions, regardless of which underlying LLM is driving the agent.

See all FAQs

From the blog

Darwinbox API Directory

Darwinbox API Directory

Learn about the common Darwinbox API data models and API end points in this comprehensive Darwinbox API directory

Put Integrations on Autopilot. Talk to Experts.

Knit is loved by customers across the globe due to our seamless product and white glove support. You'll love us too!

Talk to a Human