resume-mcp-server

resume-mcp-server

MCP server for browsing and searching your local resume and job application documents

Category
Visit Server

README

resume-mcp-server

CI License: GPL v3 Python 3.12+ MCP PyPI resume-mcp-server 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-server

Then connect Claude Code:

claude mcp add resume-collection resume-mcp-server -e RESUME_DIR=$(pwd)/sample_resumes

For 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 .env

2. Build and start

docker compose build resume-mcp
docker compose up -d

The 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/mcp

To 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 down

Docker (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-server

Claude 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-server

Or create a .env file in the directory you run the server from:

# .env
RESUME_DIR=/path/to/docs
FASTMCP_PORT=8001

Then 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/resumes

uvx:

{
  "mcpServers": {
    "resume-collection": {
      "command": "uvx",
      "args": ["resume-mcp-server"],
      "env": {
        "RESUME_DIR": "/path/to/your/resumes"
      }
    }
  }
}

Configuration

Docker Compose (.env):

Variable Description
RESUME_DIR_HOST Path on your machine to the documents directory — mounted to /resumes inside the container
FASTMCP_PORT Port the HTTP server listens on (default 8001)
LOG_LEVEL Logging verbosity: DEBUG, INFO, WARNING, ERROR (default INFO)

Local run (environment variables or .env):

Variable Default Description
RESUME_DIR ~/resumes Directory scanned for documents
FASTMCP_TRANSPORT http (local) / stdio (Docker image) Transport protocol (http or stdio)
FASTMCP_HOST 0.0.0.0 Bind address
FASTMCP_PORT 8001 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
resume contains resume
cover_letter cover letter, _cl., coverletter
application_material interview, study guide, why_, application question, job desc
other 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
doc_type string (optional) resume, cover_letter, application_material, or other

get_resume

Return the full extracted text of a document.

Parameter Type Description
path string Relative path as returned by list_resumes

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
resume_id string Resume ID from list_resume_summaries or search_resumes_by_name

search_resumes

Full-text search across all documents (case-insensitive), sorted by match count.

Parameter Type Description
query string Text to search for
doc_type string (optional) Filter by type (same values as list_resumes)

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
query 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
skill 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
query 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
query 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
resume_id string (optional) Resume ID from list_resume_summaries
current_only boolean (optional) If true, return only roles where end_date is "Present"

get_work_experience

Get a single work experience entry with its achievement bullets.

Parameter Type Description
id string Work experience ID from list_work_experiences

list_achievements

List all achievement bullets, optionally scoped to a single resume.

Parameter Type Description
resume_id string (optional) Resume ID from list_resumes

get_achievement

Get a single achievement bullet by ID.

Parameter Type Description
id string Achievement ID from list_achievements

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
query string Text to search for in achievement descriptions (case-insensitive)
resume_id 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
resume_id string (optional) Resume ID from list_resumes

get_badge_skill

Get a single badge skill by ID.

Parameter Type Description
id string Badge skill ID from list_badge_skills

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured