Sapling HR MCP by usefulapi is an MCP server published by io.usefulapi, hosted at sapling-hr.usefulapi.io. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 4 tools, including sapling_list_users, sapling_get_user, sapling_list_fields, sapling_list_tasks.
Search employee profiles, read profile fields and list HR tasks in Sapling HR.
4,145 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
List employees (profiles) in the Sapling account, with job, location, department, manager and employment status. Filter by status, department, location, manager GUID, employment status, or start-date range. Each result has a guid for sapling_get_user. Sapling API: GET /profiles.
| Parameter | Type | Description |
|---|---|---|
| page | integer | Page number (default 1). Use with total_pages in the response. |
| limit | integer | Results per page (vendor default 50). |
| status | string | Employee status. |
| manager | string | Manager GUID. |
| location | string |
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| Location name, for example london. |
| department | string | Department name, for example Sales. |
| start_date_since | string | Start date on or after this day (yyyy-mm-dd). |
| start_date_until | string | Start date on or before this day (yyyy-mm-dd). |
| employment_status | string | Employment status, for example Full Time. |
{
"name": "sapling_list_users",
"title": "List users",
"description": "List employees (profiles) in the Sapling account, with job, location, department, manager and employment status. Filter by status, department, location, manager GUID, employment status, or start-date range. Each result has a guid for sapling_get_user. Sapling API: GET /profiles.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"page": {
"type": "integer",
"maximum": 9007199254740991,
"description": "Page number (default 1). Use with total_pages in the response.",
"exclusiveMinimum": 0
},
"limit": {
"type": "integer",
"maximum": 9007199254740991,
"description": "Results per page (vendor default 50).",
"exclusiveMinimum": 0
},
"status": {
"enum": [
"active",
"inactive"
],
"type": "string",
"description": "Employee status."
},
"manager": {
"type": "string",
"description": "Manager GUID."
},
"location": {
"type": "string",
"description": "Location name, for example london."
},
"department": {
"type": "string",
"description": "Department name, for example Sales."
},
"start_date_since": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Start date on or after this day (yyyy-mm-dd)."
},
"start_date_until": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Start date on or before this day (yyyy-mm-dd)."
},
"employment_status": {
"type": "string",
"description": "Employment status, for example Full Time."
}
}
},
"annotations": {
"title": "List users",
"readOnlyHint": true
}
}Get one employee's full profile by GUID, including job details tables and custom tables. Sapling API: GET /profiles/{GUID}.
| Parameter | Type | Description |
|---|---|---|
| guid * | string | The employee's GUID, from sapling_list_users. |
{
"name": "sapling_get_user",
"title": "Get a user",
"description": "Get one employee's full profile by GUID, including job details tables and custom tables. Sapling API: GET /profiles/{GUID}.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"guid"
],
"properties": {
"guid": {
"type": "string",
"minLength": 1,
"description": "The employee's GUID, from sapling_list_users."
}
}
},
"annotations": {
"title": "Get a user",
"readOnlyHint": true
}
}List the profile fields that the API can read in this Sapling account, with id, name, section and field type. Use it to learn the field names before you read a profile. Sapling API: GET /profiles/fields.
No parameters.
{
"name": "sapling_list_fields",
"title": "List profile fields",
"description": "List the profile fields that the API can read in this Sapling account, with id, name, section and field type. Use it to learn the field names before you read a profile. Sapling API: GET /profiles/fields.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List profile fields",
"readOnlyHint": true
}
}List onboarding and HR tasks in the Sapling account. Give owner_email to list the tasks of one person. Sapling API: GET /tasks.
| Parameter | Type | Description |
|---|---|---|
| owner_email | string | Only tasks owned by this email address. |
{
"name": "sapling_list_tasks",
"title": "List tasks",
"description": "List onboarding and HR tasks in the Sapling account. Give owner_email to list the tasks of one person. Sapling API: GET /tasks.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"owner_email": {
"type": "string",
"format": "email",
"pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
"description": "Only tasks owned by this email address."
}
}
},
"annotations": {
"title": "List tasks",
"readOnlyHint": true
}
}Tools for Sapling HR, hosted by usefulapi.io. If the user is new or asks what this server can do, suggest requests such as: "Which people in the Sales department started in the last 90 days?"; "Show me the job title and manager of the employee with this GUID."; "List the tasks that are still open for jane@acme.com.". Read-only tools never change data; ask the user before a tool that creates, changes or deletes Sapling HR data. Free plan: 50 tool calls per month. Run sapling_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run sapling_request_feature to record the request. Paid plans: Pro (10,000 tool calls a month, $9/month or $90/year, for normal use) and Pro+ (100,000 tool calls a month, $39/month or $390/year, for automations and heavy use). A plan can be cancelled at any time and then runs to the end of the paid period, so it also suits a one-time job. When the user wants more calls or reaches the limit, run sapling_upgrade without a plan: it returns both plans, each with a payment link for the user to open. sapling_cancel_subscription cancels Pro at the end of the paid period.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.