MCP Connector
Rezmatch.ai ships a native MCP server, so Claude — and any MCP-capable client — can parse and match directly, no code required.
Server URL:
https://mcp.rezmatch.ai/Connect to Claude (recommended: OAuth)
- In Claude, go to Settings → Connectors → Add custom connector.
- Paste the server URL above — nothing else.
- Claude redirects you to sign in with your Rezmatch.ai dashboard account and approve access.
- Done. Tool calls now meter against your account’s credit balance.
No key to copy, no query string to build — revoke access anytime from your account.
Alternative: connect with an API key
If your client doesn’t support OAuth, append your key:
https://mcp.rezmatch.ai/access_key=rz_live_...The server also accepts Authorization: Bearer rz_live_... and x-access-key headers. Same account, same balance, whichever way you connect.
Claude Code
claude mcp add rezmatch --transport http \
"https://mcp.rezmatch.ai/" \
--header "x-access-key: $REZMATCH_API_KEY"Available tools
| Tool | Mirrors | Credits |
|---|---|---|
parse_resume | /parse/resume | 6 |
parse_jd | /parse/jd | 4 |
extract_skills | /extract/skills | 3 |
redact_text | /redact | 3 |
normalize_title | /normalize/title | 0 |
normalize_skill | /normalize/skill | 0 |
match_candidate_role | /match | 3 + inline parses |
score_requirements | /score/requirements | 3 |
Inputs and outputs are identical to the REST endpoints — the MCP server is a thin pass-through, so everything in the API Reference applies as-is, including the two promises: documents are never stored, and results are scores with explanations, never verdicts.
Example prompts
Once connected, just ask:
Parse the résumé at this URL and summarize the candidate’s experience.
Match ~/Downloads/resume.pdf against this job posting and explain what’s missing: https://job-boards.greenhouse.io/acme/jobs/123456
Claude picks the right tools, and every response includes the credits used.