Cv

io.github.francisco-perez-sorrosal由 GitHub 账号 francisco-perez-sorrosal 发布v0.0.3更新于 Oct 24, 2026

An MCP server that provides access to Francisco Perez-Sorrosal's CV

已验证STDIO仅桌面文件与存储知识与记忆

概览

AI 生成的概览

一个提供 Francisco Perez-Sorrosal 简历的 MCP 服务器,以结构化 JSON 资源形式让助手读取并查询其履历条目。

可以做什么
读取完整简历的 JSON 资源,包括简历数据与语义数据。按条目查询工作经历、教育背景、技能、出版物和专利等信息。
适用场景
适合需要助手回答关于此人职业背景的问题,或在对话中引用其简历数据的场景。
运行要求
以桌面安装包形式在用户机器上作为本地进程运行;README 另列出远程 MCP 端点。未声明账号、密钥或环境变量。需要网络访问以获取最新发布数据。
安装前请注意
服务器会自动从远程发布获取简历数据,内容来自第三方。README 描述了编辑与发布流程,会推送分支、创建拉取请求和发布标签;这些操作会改动仓库并使用 GitHub 认证,执行任何写入操作前请先确认。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Cv,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

CV Data Repository

The single source of truth for Francisco Perez-Sorrosal's CV content. YAML data, validation schema, and publishing workflow. Rendered artifacts (PDF, HTML, LaTeX, Typst, Markdown) are generated and released via GitHub Releases, never committed here.

What's here

  • cv-data/resume.yaml — structured CV content (experience, education, skills, publications, patents, etc.)
  • cv-data/resume-semantics.yaml — semantic overlay (topics, relationships, annotations)
  • schemas/ — JSON Schema for validation; mirrored from cv-forge
  • .github/workflows/ — CI validation and tag-triggered publishing

Making changes

To propose an edit to the CV data:

  1. Clone this repo and create a branch: git switch -c update/your-change
  2. Edit cv-data/resume.yaml or cv-data/resume-semantics.yaml
  3. Validate locally (see below)
  4. Push and open a PR against main

The CI workflow validates automatically; if checks pass, merge and proceed to Publishing.

Validate before you PR

bash
# Install check-jsonschema (standalone CLI)pip install check-jsonschema
# Validate both filescheck-jsonschema --schemafile schemas/resume.schema.json cv-data/resume.yamlcheck-jsonschema --schemafile schemas/semantics.schema.json cv-data/resume-semantics.yaml

All green? Ready to PR.

Publishing a release

A release is triggered by pushing a CalVer tag in the form YYYY.MM.DD (with optional .N for same-day re-releases, e.g. 2026.09.13.1).

bash
git tag 2026.09.13git push origin 2026.09.13

The workflow automatically:

  • Renders the CV in all formats (PDF, LaTeX, Typst, Markdown, HTML)
  • Publishes eight assets to the GitHub Release
  • Deploys the HTML to the live CV site
  • Creates a release.json manifest (consumed by the MCP server)

All assets are stable, version-free URLs under releases/latest/download/<name>.

Republish an Existing Release

To re-run the publish workflow without creating a new tag (useful when templates or rendering logic changes):

bash
gh workflow run publish.yml -f tag=2026.09.14

Or via the GitHub Actions UI:

  1. Open Actions → Publish CV
  2. Click "Run workflow"
  3. Enter the tag in the tag input
  4. Click "Run workflow"

This regenerates all eight release assets and redeploys the site, keeping the same version number. Assets at releases/latest/download/ are updated in place (overwritten).

Schema Updates

The JSON schemas in schemas/ are mirrored from cv-forge. When cv-forge releases a new version that changes the data models (via export-schemas), update the schemas in this repo:

  1. After cv-forge merges a PR that changes src/cv_forge/models/, refresh the mirrored copies:

    bash
    curl -s https://raw.githubusercontent.com/francisco-perez-sorrosal/cv-forge/v1/schemas/resume.schema.json > schemas/resume.schema.jsoncurl -s https://raw.githubusercontent.com/francisco-perez-sorrosal/cv-forge/v1/schemas/semantics.schema.json > schemas/semantics.schema.jsongit add schemas/git commit -m "chore: sync schemas from cv-forge v1"git push
  2. The CI drift-check (.github/workflows/validate.yml) compares the local schemas against the remote cv-forge v1 copies. If they diverge, the check fails and blocks PRs until the sync above completes. A push that lands seconds before cv-forge re-points its v1 tag can fail the drift check with a 404 on the upstream fetch; re-run the failed Validate CV Data job once the tag exists.

Consuming the CV

As data

  • YAML sources: resume.yaml and resume-semantics.yaml, published as release assets (see the URL pattern below)
  • JSON: the MCP server exposes the same data as JSON resources (fps-cv://resume, fps-cv://semantics) and per-entry lookups

As documents

  • PDF: FranciscoPerezSorrosal_CV.pdf
  • HTML (interactive): FranciscoPerezSorrosal_CV.html, also served at the live CV site
  • LaTeX (moderncv): FranciscoPerezSorrosal_CV.tex
  • Typst (moderner-cv): FranciscoPerezSorrosal_CV.typ
  • Markdown: FranciscoPerezSorrosal_CV.md

All at https://github.com/francisco-perez-sorrosal/cv/releases/latest/download/<filename>.

Via MCP

The cv Claude Code plugin connects to an MCP server that serves the CV:

text
MCP Server: https://fps-cv-mcp.wasmer.app/mcp

The server fetches the latest release data automatically; no deploy required when you publish.

Data conventions

See CLAUDE.md for entry ID scheme, cross-reference rules, date format, and validation commands.

Editing with the plugin

The cv-forge maintainer plugin provides an interactive edit flow:

  1. Launch from Claude Code: "Update my CV" or "Add this job"
  2. Edit the YAML directly in the conversation
  3. Validate automatically against the schema
  4. Preview the rendered output
  5. Diff and confirm before opening a PR

No manual YAML editing or command-line work required. The plugin uses your gh auth for the PR.

Related repositories

  • cv-forge — machinery that renders, serves, and publishes this data. Contains the CLI, MCP server, and the two Claude Code plugins (cv consumer, cv-forge maintainer).

来源:README.md,提交 d43de6c

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.0.3最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分