Connect your AI infrastructure to FormaCV with MCP
FormaCV exposes a Model Context Protocol (MCP) server so recruiters can drive CV formatting and AI tailoring from the AI tools they already use — Claude Desktop, Cursor, internal copilots, custom agents, or any MCP-compatible client. No extra charge, no add-on plan.
MCP support is included on every plan.
Why MCP matters for recruiters
Recruitment teams are building their own internal AI workflows — sourcing copilots, screening assistants, custom GPTs. Without MCP, those tools can't talk to your CV formatting platform:
Recruiters paste CVs back and forth between their AI assistant and the formatter
Internal copilots can't pull a candidate from FormaCV or push a formatted CV back
Batch operations (e.g. "format the 40 candidates in this shortlist") need manual orchestration
AI-driven tailoring instructions can't be triggered from inside the recruiter's preferred AI client
How MCP works with FormaCV
Step 1
Generate an MCP token
In your FormaCV admin, generate an MCP token scoped to a user, branch, or company.
Step 2
Connect your AI client
Add the FormaCV MCP server URL and token to Claude Desktop, Cursor, or any MCP-compatible client. Custom internal AI agents can connect via the MCP SDK.
Step 3
Drive FormaCV from your AI tool
Ask your AI ("format the 12 candidates in shortlist X to the Acme template", "tailor candidate Y to this JD and translate to English") and it executes inside FormaCV.
Step 4
Results sync back
Formatted CVs land in FormaCV, your ATS, and your AI client's context — ready for review.
What you can do via MCP
Capability
Example
Pull candidate CVs
"Get the latest CVs in shortlist Acme-Q2"
Format CVs
"Format these 12 CVs into the Acme template"
AI-tailor CVs
"Tailor each CV to this JD and bold matching skills"
Translate
"Translate the German CV to English"
Anonymize
"Anonymize for blind submission, keep university"
Push to ATS
"Attach the formatted versions to the Bullhorn candidate records"
Use case examples
Internal recruitment copilot — your in-house AI agent calls FormaCV to format and tailor CVs end-to-end
Claude Desktop / Cursor — recruiters working in their AI client of choice trigger FormaCV operations conversationally
Batch AI workflows — "for every candidate in shortlist X, tailor to JD Y and submit to client Z" runs end-to-end
Sourcing automation — sourcing tools push raw candidate inputs into FormaCV via MCP, get back branded, tailored CVs
Multi-vendor AI stacks — FormaCV slots into existing AI infrastructure without forcing recruiters to context-switch
Frequently Asked Questions
What is MCP?
Model Context Protocol is an open standard for connecting AI clients (Claude Desktop, Cursor, custom agents) to external tools and data. FormaCV implements an MCP server so any MCP-compatible client can drive CV formatting and tailoring.
Which MCP clients are supported?
Any MCP-compatible client. Today that includes Claude Desktop, Cursor, and custom agents built with the official MCP SDKs (TypeScript, Python). Recruitment teams can also build their own internal AI clients against the FormaCV MCP server.
Is MCP support included or an add-on?
Included on every plan at no extra charge — same $0.99 per-CV price applies to operations triggered via MCP.
Can MCP triggers be scoped or rate-limited?
Yes. Tokens are scoped per user, branch, or company. Audit log records every MCP-driven operation, included on every plan.
Does this replace the FormaCV UI?
No — it complements it. Most recruiters still use the FormaCV UI for review and exception handling; MCP is for the bulk and batch operations they want to drive from their AI client.
Can FormaCV pull from our own MCP servers?
In our roadmap, yes — bidirectional MCP so FormaCV can read candidate context from your internal systems. Talk to us about your specific setup.