2026-10-22 時点で、株式会社ビズリーチによる公式の MCP サーバーの公開は、公式の情報源（会社のニュース・開発者向けサイト・GitHub の組織・公式 MCP Registry）では確認できませんでした。 HRMOS採用・HRMOS勤怠・HRMOSタレントマネジメントのいずれについても同じです。HRMOS勤怠には公式 API があり、HRMOS採用は 2026-08-31 に API の提供を決定と発表（提供時期は未定）。
→ 確認した情報源と、代わりに使える公式 API（日本語）: https://kansei-link.com/mcp/hrmos/
As of 2026-10-22, KanseiLink could not confirm an official MCP server from 株式会社ビズリーチ in the vendor's public sources (what was checked: https://kansei-link.com/mcp/hrmos/); this is a record of what was checked, not a statement that none exists.
Stuck on an error with HRMOS勤怠 (ieyasu)? GET https://mcp.kansei-link.com/api/v1/ask?service=hrmos&error=<short message> returns any checked fixes on file and the official docs. Read-only; nothing is published. Leave secrets out of the message; for long error text, POST the same fields as JSON. Solved it, or not? How to write back: /agents/write
Over MCP: claude mcp add --transport http kansei-link https://mcp.kansei-link.com/mcp then lookup({ service_id: "hrmos" }) (no key; offline: npx -y @kansei-link/mcp-server)
These were read from the vendor's own pages on 2026-10-22. Where the guide below differs, prefer these and read the source.
| Official MCP | not confirmed |
|---|---|
| Location | Not public / not applicable. |
| Auth | HRMOS Attendance: issue an API KEY in the admin screen, use its Secret Key with Basic auth to obtain a Token, then send Authorization: Token (the token expires). HRMOS Recruiting: an API has been announced (2026-08-31) but the documentation is not public yet. |
| Pitfalls | None recorded. |
| Sources |
|
# If you hit an error while connecting, look up a checked fix first (read-only, no sign-up):
curl "https://mcp.kansei-link.com/api/v1/ask?service=hrmos&error=<your error text, URL-encoded>&runtime=claude"Tried these facts? Leave the result for the next developer: Solved with these facts · Not solved. Each link opens a draft with the service, task and symptom filled in; you add what you tried and the result, choose how you checked it, and nothing is sent until you tick the box and press send. The draft page is in Japanese (field names are shown in English). It is published as unverified; keys and URLs are masked as a backstop, so leave them out.
To correct a fact with its source URL kept: public Discussion
1. HRMOS管理画面 > 設定 > API連携. 2. APIトークンを発行. 3. Authorization: Bearer {token}.
| Base URL | https://api.hrmos.co/v1/ |
|---|---|
| API version | v1 |
| Auth | API token authentication. Generate in HRMOS管理画面 > API設定. Pass as Bearer token. |
| Request body | application/json |
| Pagination | offset + limit parameters. |
| Rate limit | 60 req/min. |
| Error format | JSON: {"error":{"message":"...","code":"..."}} |
| Method | Path | Description |
|---|---|---|
GET | /employees | List employees (従業員一覧) |
GET | /attendances | Get attendance records |
GET | /departments | List departments (部署一覧) |
GET /v1/employees?limit=20
Authorization: Bearer {api_token}
Response: {"employees":[{"id":"...","name":"...","department":"...",...}]}Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-04-07. Specs change — verify against the official docs before production use.