Rezi MCP
Rezi MCP
Rezi MCP lets supported AI clients connect to your Rezi account so they can read your resumes, update them, and look up jobs while helping you tailor an application.
Server URL
https://api.rezi.ai/mcp
Connect
Claude Code
claude mcp add rezi --transport http https://api.rezi.ai/mcp
Cursor
Add this to your mcp.json:
{
"mcpServers": {
"rezi": {
"url": "https://api.rezi.ai/mcp",
"transport": "streamable-http"
}
}
}
Any compatible MCP client
If your client supports remote streamable HTTP MCP servers, point it to:
https://api.rezi.ai/mcp
First-time sign in
The first time your MCP client tries to use a Rezi tool, it opens the Rezi login flow in your browser. After you sign in, the client stores the access token and keeps using it until it expires. In normal use, you only need to sign in again when that token expires or if you reconnect the server.
Available tools
| Tool | What it does |
|---|---|
list_resumes | Shows your resumes, ordered by most recently updated. |
read_resume | Returns the full JSON for a specific resume. |
write_resume | Creates a new resume or updates an existing one. |
search_jobs | Searches job listings by role and location. |
get_job_details | Fetches the full details for a job found through search_jobs. |
Typical workflows
Update an existing resume
- Use
list_resumesto find the right resume. - Use
read_resumeto load it. - Ask your AI client to make changes.
- Use
write_resumewith the updated fields.
When updating, only the fields you send are changed. Sections you do not include are preserved.
Create a new resume
Call write_resume without resume_id. Rezi creates a new resume and fills in the standard defaults needed for it to work correctly in the product.
Tailor a resume to a job
- Use
search_jobsto find a role. - Use
get_job_detailsto read the full posting. - Use
read_resumeto load your current resume. - Ask your AI client to tailor the resume for that job.
- Use
write_resumeto save the result.
Notes
- You need an active Rezi subscription to use the tools.
Session behavior and security
- Credentials are stored in memory and scoped to the MCP session ID assigned by the HTTP server.
- Session credentials are refreshed automatically when they are close to expiry.
- Resume reads and writes are performed using the authenticated user's Rezi session context.
- The service does not persist credentials to disk. If the service restarts, the user needs to sign in again.
This design keeps access aligned with the user's own Rezi permissions rather than introducing a separate privileged backend identity for resume operations.