Reactive Resume MCP Server

Free open-source resume builder with remote MCP tools for resumes and job applications. The reactive resume mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Reactive Resume is a free and open-source resume builder that simplifies the process of creating, updating, and sharing your resume.

• Real-time preview as you type
• Multiple export formats (PDF, JSON, DOCX)
• Drag-and-drop section ordering
• Custom sections for any content type
• Rich text editor with formatting support
• Professionally designed templates

Its toolset

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

• Real — time preview as you type
• Drag-and — drop section ordering
• Self — host on your own infrastructure
• Multi — language support
• PostgreSQL — Database for storing user data and resumes
• Category — Technology
• Framework — TanStack Start (React 19, Vite)
• Runtime — Node.js
• Language — TypeScript
• Database — PostgreSQL with Drizzle ORM
• API — ORPC (Type-safe RPC)
• Auth — Better Auth

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

Plenty of database access 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. Reactive Resume's toolset — Real, Drag-and, Self and 11 more — is a fair guide to whether it matches your workflow. It is maintained by amruthpillai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

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 Reactive Resume.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the reactive resume mcp server does with a few real requests.