Repository navigation
Description
👋 A self-contained first contribution: one JSON adapter file, a spec and a logo. No need to know the rest of the codebase.
Why this one
In the last 30 days, the connector search on anythingmcp.com returned nothing for Factorial HR 3 times. People want it; nobody has built it yet.
The API
- Docs: https://apidoc.factorialhr.com/
- Auth: an API key in the
x-api-keyheader (OAuth2 also exists; start with the key) - Category: HR
Suggested first tools (read-only)
list employees, get one employee, list teams, list time-off requests (leaves), list attendance shifts. Read-only tools are enough for a first version; write tools can follow in a later PR.
How
Follow the six steps in AGENTS.md → Add an adapter and docs/tool-definition.md. The scaffold command for this one:
npm run adapter:new -- factorial-hr --region intl --auth API_KEYThen node scripts/validate-adapters.mjs --warn, node scripts/regenerate-catalog.mjs, a intl/factorial-hr.live.spec.ts (static assertions always, live calls behind RUN_FACTORIAL_HR_LIVE=1), node scripts/adapter-count.mjs --check and the logo. The walkthrough and past examples are in #982.
Done when
- The adapter validates without new warnings and the catalog is regenerated.
- Every tool has a description an AI can act on (what it returns, when to use it) and a response mapping that keeps the useful fields.
- The PR says which calls you ran against a real account, or that you could not and built it from the docs.
Claim it
Comment here to claim it. A claim without a PR for 14 days goes back to the pool, no hard feelings. Sign the CLA when the bot asks.
Activity
Aadithya-kl commentedon Nov 3, 2026
I'd like to take this issue. I'll inspect the existing adapter patterns and the current Factorial API documentation, then prepare a focused read-only adapter with static tests. I'll follow the repository's contribution guide and confirm the implementation approach before opening a pull request.
helpcodeai commentedon Nov 4, 2026
Hi @Aadithya-kl, it is yours. I assigned the issue to you.
Start read-only with the
x-api-keyheader, as described above. If anything in the API looks different from the docs, write it here before you open the PR. Thanks!Aadithya-kl commentedon Nov 5, 2026
Thanks for assigning this issue!
I've implemented the Factorial HR adapter with five strictly read-only tools, using the documented
x-api-keyauthentication and Factorial API version2026-10-01.I haven't identified any API documentation discrepancies during implementation. The static tests and adapter validation are passing. Live API tests remain skipped because I don't currently have Factorial API credentials.
I'm completing the final fork and PR setup now. I'll share the PR link here shortly.
Thanks!