Laddro Career

com.laddroPublished by laddro.comOfficial publisherv0.5.1Updated Nov 2, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowMedia & DesignAI & ML

Overview

AI-generated overview

Laddro Career lets an assistant tailor resumes, generate cover letters, browse templates and export CVs as PDF through the Laddro Career API.

What you can do
  • Browse resume templates, template colors and fonts, font families and supported locales
  • List and read the user's resumes and cover letters, including metadata
  • Tailor a resume to a job posting and re-render it with new template settings
  • Create or generate cover letters from a resume and job, then render them
  • Export resumes as PDF
  • In OAuth connector mode, read resume and cover-letter JSON schemas and create or fully replace resume content
When to use it
Useful when someone wants an assistant to help with job applications: adapting an existing Laddro resume to a specific posting, drafting cover letters, or producing a styled PDF CV without leaving the chat.
Requirements
A Laddro account and API key from the Laddro console, supplied as the LADDRO_API_KEY environment variable for the local npm package or as an Authorization bearer token (or x-api-key header) for the hosted endpoint at mcp.laddro.com. OAuth is declared as required; the connector mode is behind the MCP_CONNECTOR_ENABLED flag, off by default. Node.js is needed for the npx package.
Before you install
The API key is a live credential that grants access to the user's resumes and cover letters; keep it out of shared configs. Tools create, update and re-render resume and cover-letter content, and tailoring or generation sends resume and job text to Laddro's servers. Connector mode forwards OAuth tokens to a separate Laddro backend service.

Installation

In SourceWeft

  1. Open Laddro Career in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.laddro%2Fcareer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "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

Source: README.md at commit 7eede46

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.5.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts