Laddro Career

Registre officiel Productivité

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

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http laddro-career 'https://mcp.laddro.com/mcp' --header 'Authorization: <Bearer token using your Laddro Career API key from console.laddro.com>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "laddro-career": {
            "type": "http",
            "url": "https://mcp.laddro.com/mcp",
            "headers": {
                "Authorization": "<Bearer token using your Laddro Career API key from console.laddro.com>"
            }
        }
    }
}
NPM package @laddro/career-mcp
Claude Code
claude mcp add laddro-career -e 'LADDRO_API_KEY=<your laddro_api_key>' -- npx -y @laddro/career-mcp@0.5.1
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "laddro-career": {
            "command": "npx",
            "args": [
                "-y",
                "@laddro/career-mcp@0.5.1"
            ],
            "env": {
                "LADDRO_API_KEY": "<your laddro_api_key>"
            }
        }
    }
}

Variables d'environnement

  • LADDRO_API_KEY obligatoire secret Your Laddro Career API key from console.laddro.com

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. @laddro/career-mcp
  2. Setup
  3. Available tools
  4. Connector (OAuth) mode
  5. Environment variables
  6. Development
  7. Releases
  8. MCP registry
  9. Links
  10. License

@laddro/career-mcp

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:

{
  "mcpServers": {
    "laddro-career": {
      "command": "npx",
      "args": ["@laddro/career-mcp"],
      "env": {
        "LADDRO_API_KEY": "laddro_live_..."
      }
    }
  }
}
Claude Code
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:

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_...

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

npm ci
npm 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:

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:

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

License

MIT

Questions fréquentes

Qu'est-ce que Laddro Career ?

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

Comment installer Laddro Career ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http laddro-career 'https://mcp.laddro.com/mcp' --header 'Authorization: <Bearer token using your Laddro Career API key from console.laddro.com>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Laddro Career ?

Oui. Il attend LADDRO_API_KEY, Authorization, à renseigner dans sa configuration.

Laddro Career est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient Laddro Career ?

Il est publié par laddro-app. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.