Laddro Career

com.laddro由 laddro.com 发布官方发布者v0.5.1更新于 Nov 2, 2026

Tailor resumes, generate cover letters, render CVs as PDF, and browse 22+ templates.

已验证Streamable HTTP可网页运行效率与工作流媒体与设计AI 与机器学习

概览

AI 生成的概览

Laddro Career 让助手通过 Laddro Career API 定制简历、生成求职信、浏览模板并将简历导出为 PDF。

可以做什么
  • 浏览简历模板、模板配色与字体、字体家族及支持的语种
  • 列出并查看用户的简历和求职信及其元数据
  • 针对某个职位定制简历，并按新的模板设置重新渲染
  • 根据简历和职位手动创建或 AI 生成求职信，并进行渲染
  • 将简历导出为 PDF
  • 在 OAuth 连接器模式下读取简历与求职信的 JSON Schema，并创建或整体替换简历内容
适用场景
适合求职场景：让助手把已有的 Laddro 简历针对具体职位做调整、起草求职信，或在对话中直接产出带样式的 PDF 简历。
运行要求
需要 Laddro 账号及在 Laddro 控制台获取的 API 密钥：本地 npm 包通过环境变量 LADDRO_API_KEY 提供，托管端点 mcp.laddro.com 则通过 Authorization Bearer 令牌或 x-api-key 请求头提供。声明要求 OAuth；连接器模式由 MCP_CONNECTOR_ENABLED 开关控制，默认关闭。使用 npx 包需要 Node.js。
安装前请注意
API 密钥是可直接访问用户简历和求职信的有效凭据，请勿写入共享配置。相关工具会创建、更新和重新渲染简历与求职信内容，定制与生成会把简历和职位文本发送到 Laddro 服务器。连接器模式还会把 OAuth 令牌转发给另一个 Laddro 后端服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Laddro Career，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.laddro%2Fcareer/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "laddro-career": {
      "type": "http",
      "url": "https://mcp.laddro.com/mcp"
    }
  }
}

README

@laddro/career-mcp

[smithery badge]

MCP server for the Laddro Career API. Gives AI agents access to resume tailoring, cover letter generation, PDF export, and template browsing.

Setup

Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "laddro-career": {      "command": "npx",      "args": ["@laddro/career-mcp"],      "env": {        "LADDRO_API_KEY": "laddro_live_..."      }    }  }}

Claude Code

bash
claude mcp add laddro-career -- npx @laddro/career-mcp

Set the environment variable LADDRO_API_KEY before running.

Remote HTTP

Use the hosted Streamable HTTP endpoint:

text
https://mcp.laddro.com/mcp

Send your Laddro API key on the MCP initialize request:

http
Authorization: Bearer laddro_live_...

or:

http
x-api-key: laddro_live_...

Available tools

ToolDescription
laddro.templates.listBrowse all 22 resume templates
laddro.templates.getGet template colors and fonts
laddro.fonts.listAll available font families
laddro.languages.listAll 14 supported locales
laddro.resumes.listUser's resumes
laddro.resumes.getResume metadata
laddro.resumes.renderRe-render with new template settings
laddro.resumes.tailorAI-tailor resume for a job
laddro.resumes.exportExport as PDF
laddro.coverLetters.listUser's cover letters
laddro.coverLetters.getCover letter metadata
laddro.coverLetters.createCreate manually
laddro.coverLetters.generateAI-generate from resume + job
laddro.coverLetters.renderRender with template settings

Connector (OAuth) mode

Behind the MCP_CONNECTOR_ENABLED flag (default off). When enabled and a request carries Authorization: Bearer lad_at_* (a Laddro OAuth access token), the server runs an OAuth connector session that forwards the token to laddro-backend (service.laddro.com) instead of career-api. It also serves GET /.well-known/oauth-protected-resource (RFC 9728) and answers unauthenticated /mcp calls with 401 + WWW-Authenticate: Bearer resource_metadata=... so OAuth clients can discover the authorization server. With the flag off, behaviour is unchanged (no discovery route, no 401 enforcement, all 18 tools via career-api).

Connector tools (OAuth sessions only): "You write the content. Laddro stores it and renders the PDF."

ToolScopeDescription
laddro.resume.schema—JSON Schema for resume content
laddro.resume.createresumes:writeCreate a resume, returns { resumeId }
laddro.resume.updateresumes:writeFull-replace a resume, returns { resumeId, updatedAt }
laddro.coverLetter.schema—JSON Schema for cover-letter content

Environment variables

VariableRequiredDescription
LADDRO_API_KEYYes for stdio; optional fallback for HTTPYour Laddro API key
LADDRO_BASE_URLNoOverride API URL (default: https://api.laddro.com)
MCP_CONNECTOR_ENABLEDNotrue enables OAuth connector mode (default off)
LADDRO_BACKEND_URLNoBackend base URL for connector tools (default: https://service.laddro.com)
MCP_PUBLIC_URLNoThis server's public URL for OAuth metadata (else derived from forwarded headers)

Development

bash
npm cinpm test

npm test builds the TypeScript package and runs MCP contract tests for auth handling, tool metadata, and handler routing.

Releases

This package uses Changesets and SemVer.

  • Patch: bug fixes, docs, tests, internal hardening.
  • Minor: new backwards-compatible MCP tools or capabilities.
  • Major: breaking tool names, schemas, auth, or transport behavior.

Every PR that changes the published package should include a changeset:

bash
npm run changeset

After the PR merges to main, GitHub Actions opens a release PR with the version bump and changelog. Merging that release PR publishes the package to npm and creates the GitHub release. The Cloud Run deploy workflow also runs on main, so hosted MCP updates automatically after release merges.

MCP registry

This server is listed in the official MCP registry as com.laddro/career. server.json is the registry manifest; scripts/sync-version-metadata.mjs keeps its version in sync with the npm package on every release.

Publishing is automated: .github/workflows/publish-registry.yml runs whenever a release changes server.json on main and pushes the new version to the registry. Auth is DNS-based — the Ed25519 public key lives in the laddro.com TXT record, and the matching private key (hex) is stored as the MCP_PUBLISHER_ED25519_KEY repo secret.

To publish (or catch up) manually:

bash
MCP_PUBLISHER_ED25519_KEY=<hex-private-key> ./scripts/publish-registry.sh

Links

License

MIT

来源：README.md，提交 7eede46

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

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

评分

已满足适用检查项的 85%

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

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

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

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