Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
作者提供的说明(英文原文)
Tailor resumes, generate cover letters, render CVs as PDF, and browse 22+ templates.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
LADDRO_API_KEY, Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"career": {
"command": "npx",
"args": [
"-y",
"@laddro/career-mcp"
],
"env": {
"LADDRO_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http career https://mcp.laddro.com/mcp --header 'Authorization: Bearer {LADDRO_API_KEY}'claude mcp add career --env LADDRO_API_KEY=your-value -- npx -y @laddro/career-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"career": {
"url": "https://mcp.laddro.com/mcp",
"headers": {
"Authorization": "Bearer {LADDRO_API_KEY}"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"career": {
"command": "npx",
"args": [
"-y",
"@laddro/career-mcp"
],
"env": {
"LADDRO_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"career": {
"type": "http",
"url": "https://mcp.laddro.com/mcp",
"headers": {
"Authorization": "Bearer {LADDRO_API_KEY}"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"career": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@laddro/career-mcp"
],
"env": {
"LADDRO_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 laddro.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:LADDRO_API_KEY
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(0.5.1)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Agent-Native Google Calendar - manage events, sync, and public booking
Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
MCP server for the Laddro Career API. Gives AI agents access to resume tailoring, cover letter generation, PDF export, and template browsing.
Add to your claude_desktop_config.json:
{
"mcpServers": { "laddro-career": { "command": "npx", "args": ["@laddro/career-mcp"], "env": { "LADDRO_API_KEY": "laddro_live_..." } } } }
claude mcp add laddro-career -- npx @laddro/career-mcp
Set the environment variable LADDRO_API_KEY before running.
Use the hosted Streamable HTTP endpoint:
https://mcp.laddro.com/mcp
Send your Laddro API key on the MCP initialize request:
Authorization: Bearer laddro_live_...
or:
x-api-key: laddro_live_...
| Tool | Description |
|---|---|
laddro.templates.list | Browse all 22 resume templates |
laddro.templates.get | Get template colors and fonts |
laddro.fonts.list | All available font families |
laddro.languages.list | All 14 supported locales |
laddro.resumes.list | User's resumes |
laddro.resumes.get | Resume metadata |
laddro.resumes.render | Re-render with new template settings |
laddro.resumes.tailor | AI-tailor resume for a job |
laddro.resumes.export | Export as PDF |
laddro.coverLetters.list | User's cover letters |
laddro.coverLetters.get | Cover letter metadata |
laddro.coverLetters.create | Create manually |
laddro.coverLetters.generate | AI-generate from resume + job |
laddro.coverLetters.render | Render with template settings |
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."
| Tool | Scope | Description |
|---|---|---|
laddro.resume.schema | — | JSON Schema for resume content |
laddro.resume.create | resumes:write | Create a resume, returns { resumeId } |
laddro.resume.update | resumes:write | Full-replace a resume, returns { resumeId, updatedAt } |
laddro.coverLetter.schema | — | JSON Schema for cover-letter content |
| Variable | Required | Description |
|---|---|---|
LADDRO_API_KEY | Yes for stdio; optional fallback for HTTP | Your Laddro API key |
LADDRO_BASE_URL | No | Override API URL (default: https://api.laddro.com) |
MCP_CONNECTOR_ENABLED | No | true enables OAuth connector mode (default off) |
LADDRO_BACKEND_URL | No | Backend base URL for connector tools (default: https://service.laddro.com) |
MCP_PUBLIC_URL | No | This server's public URL for OAuth metadata (else derived from forwarded headers) |
npm ci
npm test
npm test builds the TypeScript package and runs MCP contract tests for auth handling, tool metadata, and handler routing.
This package uses Changesets and SemVer.
Every PR that changes the published package should include a changeset:
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.
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:
MCP_PUBLISHER_ED25519_KEY=<hex-private-key> ./scripts/publish-registry.sh
MIT