HRtool.ai MCP server

Use HRtool.ai directly from Claude (Desktop, Code, or any MCP client) to look up and analyze assessments, surveys, live interviews, and company stats with your own words. It wraps the HRtool.ai API and authenticates with your personal API key, so everything is scoped to your company and your permissions.

What Claude can do with it

Ask things like:

• "Summarize how candidates did on the Sales assessment this month and flag the weakest questions."
• "Pull every result and meeting for [email protected] and give me a hire recommendation with evidence."
• "Which live interviews scored below 60 last week? Summarize why."
• "Compare our NPS survey results this quarter vs last."
• "Create a live meeting for John ([email protected]) using the Account Executive assessment and give me the candidate link."

Tools exposed

| Tool | What it does | |---|---| | list_assessments | Your active assessments | | create_assessment_link | Shareable candidate link for an assessment | | list_responses | Look up results (filter by assessment, email, date, keyword) | | get_response | One result in full (answers, AI analysis, media) | | get_response_media | Download URLs for recorded answers | | list_candidate_responses | All results for one candidate email | | list_meetings | Live meetings (filter by status/email/keyword) | | get_meeting | One meeting in full (AI score, summary, Q&A, transcript, recording, join links) | | get_meeting_media | Recording download URL | | list_candidate_meetings | All meetings for one candidate email | | create_meeting | Create a live meeting (returns join links) | | get_stats | Company performance + usage for a date range |

1. Get an API key

In HRtool.ai: User Settings → API keys → + New key. Copy it (shown once). You need the "Access the API" permission — a manager grants it in Company Settings → Team. Managers have it by default and can give a key to anyone they want to use this.

2. Add it to your MCP client (no install needed — uses npx)

Claude Desktop

Settings → Developer → Edit Config, then add:

{
  "mcpServers": {
    "hrtool": {
      "command": "npx",
      "args": ["-y", "hrtool-mcp"],
      "env": {
        "HRTOOL_API_KEY": "hrt_your_key_here",
        "HRTOOL_BASE_URL": "https://hrtool.ai"
      }
    }
  }
}

Restart Claude Desktop — the hrtool tools appear. npx downloads and runs the latest version automatically; no manual install.

Claude Code

claude mcp add hrtool -e HRTOOL_API_KEY=hrt_your_key_here -e HRTOOL_BASE_URL=https://hrtool.ai -- npx -y hrtool-mcp

Local / development (running from this repo instead of npx)

cd services/mcp-server && npm install
# then in the client config use:  "command": "node", "args": ["/abs/path/to/services/mcp-server/index.js"]

For the HRtool.ai team: publishing to npm

So customers can use the one-line npx config above, publish the package once (and after each change):

cd services/mcp-server
npm install
npm login            # first time only, as the account/org that owns "hrtool-mcp"
npm version patch    # bump the version
npm publish          # publishConfig.access is already "public"

To publish under an org scope instead, rename to @hrtool/mcp in package.json (and in the args customers use). Customers always get the latest via npx -y hrtool-mcp.

Notes

• Scope & permissions: a key inherits its owner's company and permissions. Revoke it any time in User Settings — it stops working immediately.
• Rate limit: 300 requests/min per company (the server surfaces a clear message on 429).
• Security: the key is a credential — keep it in the client's env config, not in shared files.
• Self-hosted / staging: set HRTOOL_BASE_URL to your instance's URL.