Search employee profiles, read profile fields and list HR tasks in Sapling HR. For HR teams that look up employee profiles and onboarding tasks in Sapling HR. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"sapling-hr": {
"url": "https://sapling-hr.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"sapling-hr": {
"type": "http",
"url": "https://sapling-hr.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Filter employee profiles by department and start-date range, then read one full profile by its GUID.
sapling_list_users sapling_get_user
List the profile fields the API can read, with their ids, sections and types, before you read a profile.
sapling_list_fields sapling_get_user
List onboarding and HR tasks, or only the tasks of one person by email.
sapling_list_tasks
The login page asks for your Sapling subdomain, Data centre and Sapling API key.
The subdomain is the part before .saplingapp.io in your Sapling web address. Create the key in Sapling → Admin Settings → Integrations → API Keys. The key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Sapling subdomain, Data centre and Sapling API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Sapling HR connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
sapling_list_users | read | List users 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. |
sapling_get_user | read | Get a user Get one employee's full profile by GUID, including job details tables and custom tables. Sapling API: GET /profiles/{GUID}. |
sapling_list_fields | read | List profile fields 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. |
sapling_list_tasks | read | List tasks List onboarding and HR tasks in the Sapling account. Give owner_email to list the tasks of one person. Sapling API: GET /tasks. |
sapling_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
sapling_request_feature | Request a missing feature Tell usefulapi that the user needs something the Sapling HR tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
sapling_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Sapling HR (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
sapling_cancel_subscription | Cancel the Pro subscription Cancel the caller's Sapling HR Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run sapling_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Sapling HR server only. Subscribe with sapling_upgrade (it returns a Stripe Checkout link). Cancel any time with sapling_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running sapling_upgrade before then undoes the cancel. Or write to [email protected].
Find people who started recently. See which profile fields the API can read. Review the open tasks of one person. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Sapling HR. The server calls the Sapling HR API with your own Sapling HR access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Sapling subdomain, Data centre and Sapling API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Sapling subdomain, Data centre and Sapling API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Sapling HR API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Sapling HR.
All 4 Sapling HR tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Sapling HR server only. Cancel any time: Pro then runs to the end of the paid period. Run sapling_usage_status to see how many calls you used.
Ask the AI to run sapling_upgrade: it returns a Stripe Checkout link. To cancel, run sapling_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with sapling_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.