Cvx MCP Server

Cvx MCP server exists for a simple reason — assistants are far more useful when they can act on Cvx directly instead of describing what you should do. Create, validate, and render CV PDFs from plain YAML — fully local, no accounts.

What you get

Structured input. Professional output. To the power of X.

What the assistant can call

Once Cvx is connected, these are the calls the assistant has available:

• role — Founder & Field Commander – Gotham Operations
• title — Commander, Batman Incorporated
• degree — "Applied Sciences & Criminology (self-directed)"
• year — Gotham's Most Influential Citizen
• name — Diana Prince
• identity-photo — contact
• summary — spacer: 27
• identity-compact — education
• competencies — achievements
• experience — continued
• Theme — Accent
• teal — #1a6070

Setting it up

@hrtips/cvx on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cvx's toolset — role, title, degree and 11 more — is a fair guide to whether it matches your workflow. It is maintained by hrtips; 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.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Cvx.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cvx mcp server does with a few real requests.