AI & Machine Learning
vitae.ai
An AI recruiting assistant MCP server that queries candidate, job, client, and pipeline data, checks agent status, shows dashboard metrics, manages approvals, and lists conversation threads.
ENDPOINT 1
https://mcp.vitae.ai/mcp
MCP server metadata
- Name
- vitae-mcp
- Version
- 0.0.1
Known tools 70
ask_vitaeAsk the Vitae recruiting agent to search candidates, jobs, clients, pipeline status, or draft workflows.
Inferred read-onlyget_dashboardGet recruiting dashboard counters: pipeline stats, activity totals, key metrics.
Inferred read-onlylist_threadsList recent Ask Vitae conversation threads for the authenticated user.
Inferred read-onlylist_archived_threadsList archived Ask Vitae conversation threads for the authenticated user.
Inferred read-onlycreate_threadCreate a new non-destructive Ask Vitae conversation thread for the authenticated user.
Potential side effectsget_search_detailsGet full details for a candidate search: prompt, filters, metadata.
Inferred read-onlyget_monitoring_profileGet the tenant's BD Signals monitoring profile: ICP context, triggers, discovery queries, source domains, and scan cadence.
Inferred read-onlyimport_campaign_contactsAtomically create or reuse up to 500 Contacts by caller-stable external identity and attach them to an existing campaign.
Potential side effectssearch_ats_candidatesSearch the candidates already saved in this account's Vitae ATS, by name, email, or skill.
Potential side effectsmove_applicationMove a candidate application to a different pipeline stage on a job.
Inferred read-onlymove_applications_bulkMove multiple candidate applications to a pipeline stage on a job in one call.
Inferred read-onlyget_best_matchesGet candidates matched to a job, ranked by their persisted match score (highest first; the same score the job's match reports show).
Inferred read-onlycount_applicationsCount applications across the WHOLE account (every job), grouped by pipeline stage, with optional stage, minimum match score, updated-since date, job, or client filters.
Inferred read-onlycount_matchesCount AI match scores across the WHOLE account (every job), optionally filtered by a score range, a job, or a client.
Inferred read-onlydescribe_query_schemaList every entity and field you can query across the account, with the operators, group-by, and aggregate options for each.
Inferred read-onlyquery_recordsRun an account-wide, org-scoped count or aggregate over an allow-listed entity (applications, candidates, jobs, clients, matches).
Inferred read-onlysave_viewSave a query_records query (entity + filters + aggregate + groupBy) under a name so it can be re-run later as a reusable segment, e.g.
Inferred read-onlylist_saved_viewsList the saved query_records segments (name + entity + filters) the user has saved.
Inferred read-onlyrun_saved_viewRe-run a saved query_records segment by name and return its current count/aggregate.
Inferred read-onlylist_candidate_poolsList candidate pools/shortlists shared across the current organization.
Inferred read-onlycreate_candidate_poolCreate a new saved candidate pool/shortlist after the user approves the pending action.
Potential side effectsupdate_candidate_poolAdd/remove candidates from a pool, or rename it, after the user approves the pending action.
Potential side effectsdelete_candidate_poolDelete a saved candidate pool after the user approves the pending action.
Potential side effectsget_interview_responseGet interview notes/rating for a specific candidate on a job.
Inferred read-onlysubmit_interview_responseSubmit recruiter interview notes and rating for a candidate on a job.
Inferred read-onlylist_workflowsList automation workflows in the tenant with their status and triggers.
Inferred read-onlylist_adaptive_dashboard_blocksList dashboard blocks the agent can compose into saved surfaces.
Inferred read-onlysave_adaptive_surface_configSave a user adaptive dashboard/report surface configuration.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vitae-mcp]
url = "https://mcp.vitae.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vitae-mcp": {
"type": "http",
"url": "https://mcp.vitae.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vitae-mcp
Remote MCP URL: https://mcp.vitae.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vitae-mcp": {
"url": "https://mcp.vitae.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vitae-mcp": {
"type": "http",
"url": "https://mcp.vitae.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vitae-mcp",
"transport": "streamable-http",
"url": "https://mcp.vitae.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.