resume-mcp-server
resume-mcp-server
An MCP server for browsing and searching job application documents — resumes, cover letters, and related materials.
Supports .docx, .pdf, .md, and .txt files, including nested subdirectories.
Quick Start
Give Claude structured access to your resume collection. The server parses your documents on startup and exposes 16 tools for searching by name, company, skill, or full text — with automatic hot-reload when files change.
Try it immediately with the included sample resumes:
pip install resume-mcp-server
RESUME_DIR=./sample_resumes resume-mcp-serverThen connect Claude Code:
claude mcp add resume-collection resume-mcp-server -e RESUME_DIR=$(pwd)/sample_resumesFor a persistent setup with Docker or your own documents, see Docker Deploy or Dev Environment.
Docker Deploy
The recommended way to run the server. Docker Compose exposes the server over HTTP so any AI client can connect to it.
1. Set your resume directory
Copy the example env file and set your documents path:
cp .env.example .env
# then edit RESUME_DIR_HOST in .env2. Build and start
docker compose build resume-mcp
docker compose up -dThe server is now available at http://localhost:8001/mcp.
3. Connect your AI client
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"resume-collection": {
"type": "http",
"url": "http://localhost:8001/mcp"
}
}
}VS Code (.vscode/mcp.json):
{
"servers": {
"resume-collection": {
"type": "http",
"url": "http://localhost:8001/mcp"
}
}
}Claude Code:
claude mcp add resume-collection --transport http http://localhost:8001/mcpTo add it globally across all projects, add the following to ~/.claude.json instead:
{
"mcpServers": {
"resume-collection": {
"type": "http",
"url": "http://localhost:8001/mcp"
}
}
}Stopping
docker compose downDocker (stdio)
Run the image directly — no Compose needed — for MCP clients that use stdio transport (including Glama.ai and Claude Desktop):
docker run -i --rm -v /path/to/your/resumes:/resumes resume-mcp-serverClaude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"resume-collection": {
"command": "docker",
"args": ["run", "-i", "--rm", "-v", "/path/to/your/resumes:/resumes", "resume-mcp-server"]
}
}
}Dev Environment
For local development or running the server without Docker.
Prerequisites
Python 3.12+
Install
pip install .
# include test dependencies:
pip install ".[dev]"Run
resume-mcp-server
# with a custom directory:
RESUME_DIR=/path/to/docs resume-mcp-serverOr create a .env file in the directory you run the server from:
# .env
RESUME_DIR=/path/to/docs
FASTMCP_PORT=8001Then just run resume-mcp-server — the .env is loaded automatically. Variables already set in your shell or by the MCP client always take precedence over .env values.
Connect your AI client (stdio)
Claude Desktop:
{
"mcpServers": {
"resume-collection": {
"command": "resume-mcp-server",
"env": {
"RESUME_DIR": "/path/to/your/resumes"
}
}
}
}If resume-mcp-server is not on your PATH, use the full path (e.g. ~/.venv/bin/resume-mcp-server).
Claude Code:
claude mcp add resume-collection resume-mcp-server -e RESUME_DIR=/path/to/your/resumesuvx:
{
"mcpServers": {
"resume-collection": {
"command": "uvx",
"args": ["resume-mcp-server"],
"env": {
"RESUME_DIR": "/path/to/your/resumes"
}
}
}
}Configuration
Docker Compose (.env):
Variable | Description |
| Path on your machine to the documents directory — mounted to |
| Port the HTTP server listens on (default |
| Logging verbosity: |
Local run (environment variables or .env):
Variable | Default | Description |
|
| Directory scanned for documents |
|
| Transport protocol ( |
|
| Bind address |
|
| Port the HTTP server listens on |
A .env file in the working directory is loaded automatically on startup if present. Shell environment variables and values set by the MCP client always take precedence over .env values.
The server scans RESUME_DIR recursively on startup and reloads automatically when files change.
Document type inference
Types are inferred from filenames:
Type | Filename patterns |
| contains |
|
|
|
|
| everything else |
MCP Tools
list_resume_summaries
List all resumes as lightweight identity records. Use this first to orient and pick a resume_id before fetching details — much more token-efficient than list_resumes.
No parameters.
Returns: id, first_name, last_name, email, phone_num for each resume.
list_resumes
List all documents, optionally filtered by type.
Parameter | Type | Description |
| string (optional) |
|
get_resume
Return the full extracted text of a document.
Parameter | Type | Description |
| string | Relative path as returned by |
get_resume_profile
Get a resume's top-level fields (contact info, professional statement, education) without the nested work experience or badge skill lists. Prefer this over get_resume when you need structured contact data rather than raw text.
Parameter | Type | Description |
| string | Resume ID from |
search_resumes
Full-text search across all documents (case-insensitive), sorted by match count.
Parameter | Type | Description |
| string | Text to search for |
| string (optional) | Filter by type (same values as |
search_resumes_by_name
Find resumes by person name (first or last name). Returns minimal identity fields — use the returned id with other tools to fetch full details.
Parameter | Type | Description |
| string | Name fragment to search for (case-insensitive, partial match) |
Returns: id, first_name, last_name, email, phone_num.
search_resumes_by_skill
Find which resumes list a given badge skill. Returns resume identity and matched skill names — more token-efficient than list_resumes when filtering by skill.
Parameter | Type | Description |
| string | Skill title fragment to search for (case-insensitive, partial match) |
Returns: id, first_name, last_name, matched_skills.
search_skills
Search badge skills (technologies, tools, languages) by title.
Parameter | Type | Description |
| string | Text to search for in skill titles (case-insensitive) |
search_work_experiences
Search work experiences by company name, position title, or achievement description bullets.
Each result includes a resume_id field identifying which resume the entry belongs to.
Parameter | Type | Description |
| string | Text to search for (case-insensitive) |
list_work_experiences
List work experience entries, optionally scoped to a single resume and/or only current roles.
Parameter | Type | Description |
| string (optional) | Resume ID from |
| boolean (optional) | If |
get_work_experience
Get a single work experience entry with its achievement bullets.
Parameter | Type | Description |
| string | Work experience ID from |
list_achievements
List all achievement bullets, optionally scoped to a single resume.
Parameter | Type | Description |
| string (optional) | Resume ID from |
get_achievement
Get a single achievement bullet by ID.
Parameter | Type | Description |
| string | Achievement ID from |
search_achievements
Search achievement descriptions directly, returning only matching bullets with minimal parent context. More token-efficient than search_work_experiences when you only need matching bullets.
Parameter | Type | Description |
| string | Text to search for in achievement descriptions (case-insensitive) |
| string (optional) | Resume ID to scope the search to one resume |
Returns: id, desc, company_name, position_title, work_experience_id, resume_id.
list_badge_skills
List all badge skills, optionally scoped to a single resume.
Parameter | Type | Description |
| string (optional) | Resume ID from |
get_badge_skill
Get a single badge skill by ID.
Parameter | Type | Description |
| string | Badge skill ID from |
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mnoomnoo/resume-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server