AI-NATIVE

MCP server — hire from Claude Code or Cursor

Gaugely ships a remote MCP server, so your AI assistant can run your hiring in plain language. Connect Claude Code, Cursor or VS Code with an API key and say "create an interview from this JD", "invite these 40 candidates", or "who are my top 3 for the frontend role?" — the same guardrails as the app apply.

“create interview”“invite 40”“top 3?”MCPGaugely
Start free — 12 interviews
  • →Works with Claude Code, Cursor, VS Code and any MCP client that accepts a bearer key
  • →Create interviews from a JD, build packs, and generate invite links by asking
  • →Bulk-invite candidates and pull ranked results without opening a dashboard
  • →Bearer API-key auth, managed in Settings → API & integrations
ONE TOOL, THE WHOLE TOP OF FUNNEL

Gaugely closes the loop: screen CVs → interview the best (voice or video) → compare scorecards → re-engage your past top candidates. No other tool feeds your own interview signal back into screening.

AI voice interviews & phone screens →Automatic candidate feedback →AI CV screening & ranking →Bulk interview invites from a CSV →AI job description generator →Candidate scorecard comparison →Live interviews with AI scorecards →Async one-way video interviews →Interview integrity & fraud detection →Applicant tracking & candidate database →Automated reference checks →

Questions

Which AI recruiting tools have an MCP server?

Gaugely exposes a remote MCP server out of the box. Add it to Claude Code, Cursor, VS Code and other MCP clients that let you set an Authorization header, authenticate with an API key, and run screening — create interviews, invite candidates, fetch top results — from chat.

How do I connect Claude or ChatGPT to it?

In Gaugely, open Settings → API & integrations to copy the MCP URL and create an API key. In Claude Code, Cursor or VS Code, add a remote (HTTP) MCP server with that URL and send the key as an "Authorization: Bearer" header — that's the whole setup. The Claude.ai and ChatGPT apps can't use it yet: their connectors require OAuth sign-in rather than an API key.