Point your assistant at this server

This is the whole product. Once an assistant is connected, everything happens in ordinary sentences — there is no interface to learn and nothing to keep open.

The endpoint

https://hrms.cleartrust.cc/mcp

It speaks MCP over streamable HTTP, and authorises with OAuth 2.1 — most clients will walk you through signing in the first time. If yours wants a key instead, mint one on your account page.

Claude Code

claude mcp add --transport http hr https://hrms.cleartrust.cc/mcp

Anything that takes a config file

{
  "mcpServers": {
    "hr": {
      "type": "http",
      "url": "https://hrms.cleartrust.cc/mcp",
      "headers": { "Authorization": "Bearer hrk_your_key" }
    }
  }
}

Leave the header out if your client does OAuth — it will get its own token.

Then just ask

If you work here

  • “How much leave have I got left?”
  • “Book me the 14th to the 18th off.”
  • “Half day Friday afternoon — put it through.”
  • “Did my punch-out register yesterday?”
  • “Am I entitled to casual leave yet?”

If you manage people

  • “What is waiting on me?”
  • “Who is out next week, and how thin does Thursday get?”
  • “Approve Priya’s sick leave.”
  • “Who on my team hasn’t marked their days?”

If you run HR

  • “Onboard Sofia — designer, Product, starting the 1st.”
  • “Whose probation is ending this month?”
  • “Post everyone’s accrual for August.”
  • “How much unused leave are we carrying?”
  • “Record that Arjun is leaving on the 31st; move his reports to Vikram.”

Worth knowing

  • An assistant sees exactly what you see — its key carries your role
  • Ask it to meta.whoami if an answer looks thinner than expected
  • Nothing leaves a balance until leave is approved
  • Refusals say what would fix them, and when they can be overridden

If it does not connect