What the Evander MCP server is
Evander is an applicant tracking system (ATS) with an official Model Context Protocol (MCP) server. MCP is the open standard that lets AI assistants such as Claude, ChatGPT and Cursor use outside tools. Once connected, your assistant works on your real hiring pipeline: it can create a job, list and rank applicants, move candidates between stages, schedule interviews, draft and send emails, write automations and pull reports.
Every action in the Evander web app is also an MCP tool. There is no reduced "AI subset": the app, the REST API and the MCP server are generated from the same action catalog, more than 100 actions in all.
How to connect an assistant
Sign in at app.getevander.app, open Settings → Integrations and pick your assistant. Evander creates a private MCP link for that one assistant and shows the steps.
| Assistant | How to connect |
|---|---|
| Claude (web, desktop, mobile) | Settings → Connectors → Add custom connector, then paste your Evander link. |
| ChatGPT | Settings → Apps & Connectors → Advanced settings → turn on Developer mode, create a connector with your Evander link and choose "No authentication" (the link itself is the credential). |
| Cursor | Click "Add to Cursor" in Evander, or open Cursor Settings → Tools & MCP → New MCP server and paste the configuration shown. |
| Claude Code | Run claude mcp add --transport http evander <your link>. |
| Any other MCP client | Use the link as a remote (streamable HTTP) MCP server. |
Each connected assistant gets its own identity in the workspace. An admin can see every assistant that is connected and revoke any of them with one click.
What you can ask
- "Post a founding engineer role. New York, $180–220k plus equity, TypeScript and Postgres."
- "Who are the five strongest applicants for Account Executive, and why?"
- "Where is the AE pipeline stuck?"
- "Send Priya a booking link for the technical interview."
- "When someone moves to onsite, email the prep doc and remind interviewers after 24 hours."
- "Reject everyone who scored below 40 for the designer role, with the standard rejection email."
- "How long did our last three hires take, and where did the candidates come from?"
The tools
| Area | What an assistant can do |
|---|---|
| Jobs | Create a job from a description, edit it, write the job post, set stages, scorecards and screening brief, open and close postings. |
| Candidates | Search, read and update profiles, add candidates, merge duplicates, attach files and read resumes, add notes and tags. |
| Pipeline | List and filter candidacies, move, reject, reopen and hire, alone or in bulk, with a preview of what a bulk change would do. |
| Screening | Read each applicant's score with the check behind every requirement, mark as reviewed, see scoring status. |
| Interviews | Schedule, reschedule and cancel interviews, send booking links, draft scorecard feedback, read the debrief. |
| Read candidate messages, use templates, draft and send emails from the recruiter's mailbox. | |
| Offers | Create an offer, submit it for approval, send it and record the outcome. |
| Automations | Create a workflow from a sentence, list runs, edit and delete workflows. |
| Reports | Funnel per job, candidate sources and time to hire. |
| Imports | Start an import from a CSV or an export of another ATS, map the columns and run it. |
| Workspace | Daily brief, the needs-attention list, careers page settings, invitations. |
What keeps it safe
- An assistant holds less access than a person. Mailing a candidate becomes a proposal that a person approves in Evander or Slack. Erasing candidate data, changing who has access and changing workspace settings are not open to an assistant by default and can at most be proposals. An assistant can never approve its own proposal.
- Dry runs. Every tool accepts a dry run that returns what would change and then rolls back, and a simulate tool does the same for a plan of up to 50 steps.
- No double sends. Writes that reach the outside world, such as an email or an interview invitation, carry an idempotency key, so a retry never sends twice.
- Audit log. Every change is recorded with who or what made it: a person, an assistant or an automation.
- Private data stays private. Voluntary equal-opportunity answers are never returned to an assistant, and reads of candidate data by assistants are logged.
Which hiring actions an assistant should do alone, and Evander's default for each, is in the AI assistant permission table.
Why an ATS needs an MCP server
Most hiring work is small, repeated decisions spread over many screens: read an application, compare it with the role, reply, schedule, chase feedback. An assistant with access to the pipeline can do the reading, drafting and chasing, and leave the decisions to you. That only works when the ATS exposes its full set of actions with permissions and approvals, which is what MCP standardizes.
For how other applicant tracking systems handle this, see which ATS products have an MCP server. These docs are also on GitHub.
Questions
Does Evander have an MCP server?
Yes. Evander ships an official remote MCP server. Every action in the web app is also an MCP tool, more than 100 in all, so Claude, ChatGPT, Cursor, Claude Code and other MCP clients can run hiring on your real pipeline.
How do I connect Claude or ChatGPT to Evander?
Sign in at app.getevander.app, open Settings → Integrations and choose your assistant. Evander creates a private MCP link for it. In Claude, add it under Settings → Connectors → Add custom connector. In ChatGPT, turn on Developer mode under Settings → Apps & Connectors and create a connector with the link.
Can an AI assistant reject or email candidates on its own?
Not without a person. Emails to candidates, data erasure, access changes and workspace settings become proposals that a person approves. An assistant can never approve its own proposal, and every change is written to the audit log.
Which plan includes the MCP server?
Claude, ChatGPT, Codex and Cursor are part of the Startup plan, which starts at $79 a month billed yearly and has a 14-day free trial.
How does an assistant sign in to Evander?
Each assistant gets its own private MCP link, and the link is its credential: whoever has it acts as that assistant, with no more access than the person who created it. Treat it like a password. An admin sees every connected assistant under Settings → Integrations and can revoke any link with one click. Sign-in through OAuth is not offered yet.
How should I try the MCP server safely?
Start with reads such as "list my open jobs" and "who applied this week?". Then ask for a dry run of a change: every tool can return what it would do and roll back. Changes that reach candidates, such as emails, become proposals you approve before anything is sent.
Is there a REST API as well?
Yes. The REST API and the MCP server are generated from the same action catalog, so they offer the same actions with the same permissions.