ProductIntegrations

Plugs into the tools your team depends on.

Vitae is the ATS and CRM that adapts to your business. Native MCP for the AI you bring. Supported connections for communication, data and workflow actions. A managed migration plan for the records your business depends on.

Looking for the records themselves, custom fields, and live enrichment? See the data model →

01The platform/ four pillars

Built for the AI you already use.

Most ATSs were built before LLMs. Vitae was built around them.

MCP

Connect the AI you use

Use supported Vitae tools from an MCP-compatible client such as Claude or ChatGPT. Access follows authentication, permissions and the available tool catalogue.

API

Build against a documented contract

Use the versioned REST API, served OpenAPI specification and supported webhooks. Confirm the endpoints and scopes needed for your integration.

Connections

Start with the data flow

Some connections support account sync, others power workflow actions, imports or enrichment. Agree what needs to move, in which direction and how often.

Migration

A managed move to Vitae

Scope the export, field mapping, history and attachments with our team. Validate the imported data and agree a cutover plan before switching systems.

02The connectors/ supported providers

Connected to your recruitment workflow.

The catalogue includes different connection types. Provider availability, permissions and supported operations vary; a listing does not imply complete two-way sync.

Email and calendar

Connected accounts
  • Gmail
  • Outlook
  • Google Calendar
  • Microsoft Calendar

Contact data

Provider connections
  • Apollo
  • Clay
  • ContactOut
  • LeadMagic
  • Wiza
  • Exa

Messages and notifications

Channel-specific
  • WhatsApp Business
  • Twilio
  • LinkedIn Messaging
  • Slack
  • Resend

HR and signatures

Provider connections
  • AFAS
  • Nmbrs
  • Loket
  • Exact
  • Personio
  • DocuSign

ATS and CRM

Import or workflow
  • Greenhouse
  • Lever
  • JobAdder
  • HubSpot
  • Pipedrive

Job distribution

Provider-specific
  • LinkedIn Jobs
  • Indeed
  • Volcanic

Accounting and content

Provider connections
  • Xero
  • Canva
  • Google Drive
  • Loom

Campaigns and automation

Provider connections
  • Instantly
  • Beehiiv
  • Buffer
  • Apify

Build against the published contract. Explore the API, OAuth and MCP documentation →

03Connect your AI/ two ways

Connect with the right permissions.

Point your AI client at the Vitae MCP server. One endpoint, no glue code.

MCP endpointhttps://mcp.vitae.ai/mcp
One-click OAuth

Claude and ChatGPT

Add a custom connector in your client, paste the endpoint, and approve the Vitae consent screen. The client mints and stores its own token. No secret to manage.

Access token

Any other client

Generate a personal access token in Vitae settings and send it as a bearer credential. Works with any client that supports the Streamable HTTP transport.

04Integrations FAQ/ four questions

Questions about integrations.

Short answers to the questions we get most often. Need more detail? Book a demo.

Model Context Protocol lets an AI client call supported tools. Vitae provides an authenticated MCP server with a defined tool catalogue. It is not unrestricted access to every product action.
Related reading

Build the right toolset.

The tools worth evaluating, what AI-native software actually means, and where agents fit in.

Recruitment AI

Top AI-Powered Recruitment Platforms

April 8, 2026 · 8 min read
Recruitment AI

AI Should Run Hiring, Not Just Track It

April 29, 2026 · 6 min read
AI News

Agentic AI: Recruitment After CES 2026

March 11, 2026 · 6 min read

One platform. Every tool you use.

Map the tools, data and workflows your team relies on. We will help you plan the right connections and migration.

Start for freeBook a demo