Laddro Career MCP Server

MCP server for the Laddro Career API. Exposed over MCP by the laddro career mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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

Its toolset

Everything the assistant can do here goes through one of these:

• 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.models.list — AI providers for BYOK
• 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

Configuration

You will need 5 environment variables: LADDRO_API_KEY, LADDRO_BASE_URL, LADDRO_BACKEND_URL, MCP_PUBLIC_URL, MCP_PUBLISHER_ED25519_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Laddro Career MCP's toolset — laddro.templates.list, laddro.templates.get, laddro.fonts.list and 11 more — is a fair guide to whether it matches your workflow. It is maintained by laddro-app; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Laddro Career MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the laddro career mcp mcp server does with a few real requests.