cv-builder

cv-builder

Provides MCP tools for managing a CV as structured content, including a SQLite-backed snippet library with tools to list, create, update, and match job postings, compose role-tailored CV variants, and manage drafts.

Category
访问服务器

README

CV Builder

A self-hosted tool for maintaining a CV as structured content instead of a single hand-formatted document: a browser editor for a data-driven HTML/CSS resume, a SQLite-backed snippet library for assembling role-tailored variants, and an MCP server so an LLM can help do the same thing from a chat client instead of the browser.

Ships with a fully synthetic example person in cv/web/data.yaml and content/ — replace it with your own before you rely on this for real. Nothing in this repo is anyone's real personal data.

Layout

  • cv/web/ — HTML/CSS CV source (data.yaml, template.html.j2, style.css, editor.js) and the app UI (cv/web/src/: shared shell
    • design tokens in shell/ and theme.css, one Jinja page + CSS/JS per app-chrome route under pages/)
  • content/ — optional additional detail for the snippet library, as markdown alongside data.yaml:
    • work-experience/ — one file per employer (category: experience, company taken from the filename)
    • parts/ — reusable blocks not tied to an employer, e.g. an alternate bio or a longer "detailed" variant of a strength (category: part)
    • requirements/ — pre-written answers to recurring posting requirements, for match_job_posting/the builder's posting-matcher to surface (category: requirement)
    • See the example files under each for the heading convention: only the last heading before a block of prose becomes a snippet
  • src/cvbuilder/ — snippet library (SQLite), importer, matcher, composer, and the MCP server
  • scripts/ — CLI entry points (see below)
  • data/ — SQLite snippet database (snippets.db, gitignored, regenerable) and generated variants live under cv/variants/

Quickstart

pip install -r requirements.txt

# Seed the snippet database from cv/web/data.yaml + content/
PYTHONPATH=src python3 scripts/seed-snippets.py

# Run the editor / builder / variants UI
python3 scripts/serve-editor.py        # http://127.0.0.1:5057/cv/web/edit

Requires google-chrome or chromium on PATH for PDF export (CHROME_BIN env var to point at a specific binary).

Editing in the browser

scripts/serve-editor.py serves one app, sharing a common nav/header shell (cv/web/src/shell/) across every page below except /cv/web/edit, which renders the CV document itself:

  • /cv/web/ — Home dashboard: live snippet/version counts and recent versions.
  • /cv/web/edit — click any text to edit it in place; hover controls add/reorder/delete list items (bullets, skills, jobs, subsections, education, custom side panels); Save & Preview renders a real PDF. Adding a skill/bio paragraph/education entry opens a picker fed from the snippet database, with search and duplicate flagging.
  • /cv/web/build ("Tailor") — paste a job posting to re-rank snippets by keyword match, choose content, assemble an ordered draft, and compose it into a new named variant under cv/variants/<name>/.
  • /cv/web/library ("Content library") — browse/search/filter every snippet, switch between its brief/standard/detailed variants, and create/edit/delete snippets or re-seed the database from source files.
  • /cv/web/variants ("Versions") — preview, re-render, or delete composed variant folders.
  • /cv/web/assets — browse/upload photos and logos (backed by the /api/images* endpoints) and reference the built-in contact icons.
  • /cv/web/connect ("Connect AI") — MCP setup instructions and an optional local connectivity check.

Docker

Runs the editor/builder UI and the MCP server in one container, with the repo bind-mounted so edits land on the host:

docker compose up --build
# home:     http://127.0.0.1:5057/cv/web/
# editor:   http://127.0.0.1:5057/cv/web/edit
# tailor:   http://127.0.0.1:5057/cv/web/build
# library:  http://127.0.0.1:5057/cv/web/library
# variants: http://127.0.0.1:5057/cv/web/variants
# assets:   http://127.0.0.1:5057/cv/web/assets
# connect:  http://127.0.0.1:5057/cv/web/connect
# MCP:      http://127.0.0.1:8765/mcp  (streamable-http)

Both ports publish to 127.0.0.1 only. Set ENABLE_MCP=0 in the compose environment block to run the web UI without the MCP server.

Connecting an LLM (MCP server)

src/cvbuilder/mcp_server.py (run via scripts/mcp-server.py) exposes the snippet library and composer as MCP tools: list_snippets, get_snippet, create_snippet, update_snippet, add_snippet_variant, delete_snippet, delete_snippet_variant, match_job_posting, compose_cv, list_variants, list_drafts, get_draft, save_draft, delete_draft, reseed_snippets.

Local subprocess (stdio) — the client spawns the server itself:

claude mcp add cv-builder -- python3 /absolute/path/to/cv-builder/scripts/mcp-server.py
{
  "mcpServers": {
    "cv-builder": {
      "command": "python3",
      "args": ["/absolute/path/to/cv-builder/scripts/mcp-server.py"]
    }
  }
}

Already-running server (HTTP) — point a client at the Docker container instead (MCP_TRANSPORT=streamable-http inside the container, published at http://127.0.0.1:8765/mcp):

claude mcp add --transport http cv-builder http://127.0.0.1:8765/mcp
{
  "mcpServers": {
    "cv-builder": { "url": "http://127.0.0.1:8765/mcp" }
  }
}

There's no authentication on the MCP endpoint or the web UI — fine for local personal use, but don't publish either port beyond 127.0.0.1 without adding auth first.

Set SNIPPETS_DB to point either server at a different database file (defaults to data/snippets.db).

API endpoints (same Flask process as the editor)

  • GET /api/person — read-only person block of data.yaml (Assets page)
  • GET/POST/PUT/DELETE /api/snippets — list/create/update/delete snippets
  • DELETE /api/snippets/<id>/variants/<level> — remove one detail level
  • POST /api/structure — insert/delete/move/replace items in data.yaml
  • GET /api/history, POST /api/undo, POST /api/redo — editor undo/redo
  • GET/PUT/DELETE /api/drafts[/<name>] — saved builder drafts
  • POST /api/match — rank snippets against posting text
  • POST /api/compose — compose a named variant from selected snippet ids
  • GET/DELETE /api/variants[/<name>], POST /api/variants/<name>/render
  • GET /api/images, POST /api/images/upload, POST /api/images/fetch — list, upload, or download images/icons into assets/images/
  • POST /api/seed — re-seed the database from YAML + markdown sources

Tests

python3 -m pytest

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选