Jobseeker Mcp

Standard Workflow

1. Decide whether the user wants fixture, live, or auto mode.
2. For live mode, inspect or create assets/jobseeker-mcp-runtime/jobseeker.config.json.
3. Check whether cookies are configured for the requested platform.
4. Build or test the bundled runtime before claiming the package is ready.
5. Use CLI commands for operational tasks unless the user explicitly asks for MCP server setup.

Working Directory

Run build, test, and runtime commands from:

skills/jobseeker-mcp/assets/jobseeker-mcp-runtime

Common Commands

Build:

npm run build

Test:

npm test

Start stdio MCP server:

node dist/mcp.js

Start HTTP MCP server for OpenClaw direct discovery:

node dist/mcp-http.js

Open manual login browser:

npm run dev -- login --platform boss

Run fixture-mode pipeline:

npm run dev -- run --platforms zhilian,boss,liepin --keywords llm --resume /path/to/resume.pdf --source-mode fixture

Run live-mode pipeline:

npm run dev -- run --platforms boss --keywords llm --resume /path/to/resume.pdf --source-mode live

Cookie-Based Live Mode

• Copy jobseeker.config.example.json to jobseeker.config.json.
• Fill platforms.<platform>.cookies with Playwright-compatible cookies.
• Use only the cookies required for the target site.
• If cookies are stale, fall back to manual login and refresh the browser session.

OpenClaw Notes

• Copy the jobseeker-mcp folder into a skills/ directory in an OpenClaw environment.
• The skill includes the runtime project under assets/jobseeker-mcp-runtime.
• For direct OpenClaw MCP discovery, start node dist/mcp-http.js and point the OpenClaw MCP client to http://127.0.0.1:3000/mcp.
• Use assets/jobseeker-mcp-runtime/openclaw.integration.example.json as the integration template.