iviec-mcp

MCP server exposing the iVIEC recruitment platform public API to Claude (Desktop / Code) and any other MCP-compatible client.

Setup

1. In iVIEC admin: Tuỳ chỉnh chung → Tuỳ chỉnh → Integration token, create a token and copy it.
2. Install:

   npm install
   npm run build

3. Configure your MCP client. Example for Claude Desktop (claude_desktop_config.json):

   {
     "mcpServers": {
       "iviec": {
         "command": "node",
         "args": ["/absolute/path/to/iviec-mcp/dist/index.js"],
         "env": { "INTEGRATION_TOKEN": "your_token_here" }
       }
     }
   }

Optional env: API_BASE_URL (defaults to https://public-api.iviec.vn — set to staging URL to switch).

Tools

| Tool | Purpose | | --- | --- | | iviec_list_recruitments | List recruitment requirements (job postings). | | iviec_get_recruitment | Detail of one recruitment requirement. | | iviec_list_candidates_by_recruitment | Paginated list of applicants for a recruitment. | | iviec_get_candidate | Standard candidate profile. | | iviec_get_candidate_full | Full HR record (identification, education, bank, etc.). | | iviec_update_candidate_step_and_status | Move candidate(s) through the pipeline and/or set a result state. | | iviec_lookup | Master data: business sectors, countries, provinces, districts, job categories/sources/positions, members, organization policies. |

Notes

• Token is read from INTEGRATION_TOKEN env var only — never passed as a tool argument.
• iviec_update_candidate_step_and_status enforces the API rule that only one result type may be set per call.
• More endpoints (create/update recruitment, file upload, step-only / result-only updates) can be added next; see api_doc.md.