Skip to main content
TalentReview runs two MCP servers, one for recruiters and one for candidates. Each has its own URL and its own sign-in. Both use Streamable HTTP and OAuth 2.0: your client opens a browser window, you sign in with your TalentReview account, and that’s it. There is no API key to copy, and API keys are not accepted. The setup steps below use the recruiter URL. For the candidate server, swap in https://mcp.talentreview.ai/candidate/mcp and a different name, such as talentreview-candidate.

Connect your client

Start Claude Code, type /mcp, pick talentreview and choose Authenticate. Sign in in the browser window that opens.

Recruiter tools

A few things work the same as in the dashboard:
  • Analyses and talent searches count against your plan’s monthly allowance. Repeating the same search in the same month is free.
  • When a bulk analysis would go over your allowance, the newest applicants are scored first and the rest are left out.
  • Talent search never returns a candidate’s email or phone. Use invite_to_apply instead.
  • download_cv and export_applicants_csv return a link that works once and expires after 15 minutes. You can open it in a browser without signing in.
Things to try:
  • “Who are the strongest applicants for the backend role?”
  • “Score everyone who applied to the designer job.”
  • “Find senior Go engineers in Dubai who can join within a month.”
  • “Send me a spreadsheet of this week’s applicants.”
The old SSE endpoint, https://mcp.talentreview.ai/sse, has been retired. If your connector still uses it, remove it and add https://mcp.talentreview.ai/mcp.

Candidate tools

The candidate server only sees the signed-in candidate’s own CV. Every edit is saved as a new version, so nothing is overwritten. Things to try: “Read my CV and tighten the summary”, or “Add my new job at Acme and make it the active version”.