cv-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cv-mcp compare my CV to this job description and suggest improvements"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
cv-mcp
An MCP server (TypeScript, stdio) that exposes my CV to AI assistants such as Claude. It reads the CV from a backend REST API (GET /api/cv, Spring Boot + MongoDB), so the data lives in one place and the assistant always sees the current version.
Claude Desktop <-- stdio --> cv-mcp (Node.js) <-- HTTPS --> REST API <--> MongoDBWhat it exposes
Type | Name | Description |
Tool |
| Returns the full CV as text. |
Tool |
| Lists the CV section titles. |
Tool |
| Returns one section by name (exact match first, then partial). |
Tool |
| Searches a term (technology, company, keyword) and returns the lines where it appears. |
Resource |
| Full CV text, attachable as context. |
Prompt |
| Compares the CV against a job description and suggests improvements. |
Tool descriptions and the prompt are written in Portuguese.
Related MCP server: Interactive Curriculum MCP Server
Requirements
Node.js 18 or newer (
node --version)A backend that serves the CV as JSON (see Backend contract)
Install
git clone <this-repo-url>
cd cv-mcp
npm install
npm run buildThe server is configured through one environment variable:
Variable | Description |
| Full URL of the CV endpoint, e.g. |
Use with Claude Desktop
Open Settings → Developer → Edit Config and add the server to claude_desktop_config.json (keep any servers you already have):
{
"mcpServers": {
"cv-tomas": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/cv-mcp/build/index.js"],
"env": { "CV_API_URL": "https://your-backend.example.com/api/cv" }
}
}
}Use an absolute path. On Windows, escape the backslashes:
"C:\\Users\\you\\cv-mcp\\build\\index.js".Claude Desktop does not pass your terminal's environment variables to the server, so
CV_API_URLmust be in theenvblock.Fully quit Claude Desktop (including the system tray icon) and reopen it after editing the config.
Config file locations:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonWindows (Microsoft Store install):
%LOCALAPPDATA%\Packages\Claude_*\LocalCache\Roaming\Claude\claude_desktop_config.json
Then ask Claude something like "Use list_sections" or "What TypeScript experience does Tomás have?".
Test without Claude
Use the MCP Inspector. It does not forward your shell's environment variables to the server, so pass the variable with -e:
npx @modelcontextprotocol/inspector -e CV_API_URL=https://your-backend.example.com/api/cv node build/index.js(npm run inspect starts the Inspector too; in that case add CV_API_URL under Environment Variables in the Inspector UI before connecting.)
To test the backend on its own: curl https://your-backend.example.com/api/cv.
Backend contract
GET CV_API_URL must return JSON. Each top-level key becomes a CV section (for example personalInfo, experience, education, skills, languages, volunteer). Details:
A one-element array is unwrapped to its single object.
Technical fields (
id,_id,_class) are dropped at any depth.Responses are cached in memory for 10 minutes.
Requests time out after 60 seconds, to tolerate free-tier hosts that sleep.
Troubleshooting
First request is slow or times out: free-tier backends sleep when idle. Wait about a minute and try again.
Server does not show up in Claude Desktop: invalid JSON in the config, or the path to
build/index.jsis not absolute.CV_API_URLis not set: add it to theenvblock of the config (Claude Desktop) or pass it with-e(Inspector).See errors: Claude Desktop → Settings → Developer → click the server → Logs.
Project structure
src/index.ts MCP server: tools, resource, prompt, stdio transport
src/cv.ts Fetches the CV from the API, caches it and splits it into sections
build/ Compiled output (generated by `npm run build`, not committed)With stdio, the server must never write to stdout (console.log corrupts the protocol); logs go to stderr via console.error.
License
Available Tools
4 toolsget_cvA
Devolve o CV completo do Tomás Francisco, em texto.
Inputs: no named parameters.
get_sectionA
Devolve o conteúdo de uma secção do CV. Usa list_sections para ver os nomes.
Inputs: name (required).
list_sectionsB
Lista os títulos das secções do CV (ex.: experiência, formação, competências).
Inputs: no named parameters.
search_cvA
Pesquisa um termo (tecnologia, empresa, palavra-chave) no CV e devolve as linhas onde aparece.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a clearly distinct retrieval mode: full CV, section listing, section content, and keyword search. No overlapping purposes cause confusion.
All tool names follow a consistent verb_noun snake_case pattern (get_cv, list_sections, get_section, search_cv), making the set predictable.
Four tools are well-matched to a simple CV reader, covering full retrieval, section discovery, section retrieval, and search without redundancy.
The read-only surface is complete for a static CV: full text, structured sections, section-level access, and keyword search cover all likely agent needs.
Maintenance
Related MCP Connectors
The career management plugin for your own AI assistant: CVs, cover letters, interviews and more.
Your career in your AI assistant: CV, stories, job tracker and network, read and saved back.
Build, improve and share your resume, and run your job search, from your AI assistant.
A job-search companion: tailor your CV to a role, score fit, fix ATS issues. Also via MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceExposes a structured professional resume as a set of AI-queryable tools, enabling AI clients like Claude Desktop to query summary, experience, skills, projects, and tailor resumes to job descriptions.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and LLM clients to query a professional CV and portfolio, including work history, technical skills, projects, job compatibility evaluation, education, and contact details.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to tailor a resume to any job description by extracting keywords, analyzing gaps and ATS compliance, managing versions, and compiling PDF/LaTeX outputs entirely locally without external API keys.MIT
- AlicenseAqualityBmaintenanceServes CV content in Markdown, PDF, LaTeX, HTML, and Typst formats, with semantic querying and tailored CV rendering capabilities.16MIT