MCP server
The mock HR/ATS tools, exposed over the Model Context Protocol so any MCP client (Claude Desktop, the MCP Inspector) can drive them directly. It reuses the exact same tool definitions as the in-app agent — one source of truth for both.
MCP runs locally over stdio — a client launches the server as a subprocess — so it can't be clicked from a web page the way the chat and agent can. The Agent page runs these identical tools live in your browser: same code, different transport.
Exposed tools
Loading…
How a client connects
An MCP client such as Claude Desktop starts the server as a subprocess and talks to it over stdin/stdout. On connecting it asks which tools exist and gets the list above, with each tool's description and parameters. From then on, when you ask Claude something like “which employees are in Engineering?”, the model picks a tool, the client calls it, and the server runs it against the same service layer the REST API and the agent use. Business rules apply identically: an approval that exceeds an employee's balance is refused here too.
Try the same tools live → · Source code available on request.