Resume vs Reactive Resume

In-depth architectural comparison of the Resume and Reactive Resume MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

R

Choose Resume when:

• You need dedicated capabilities in the Workplace & Productivity domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: profile_set, profile_get, resume_create.

Explore Resume Details

Choose Reactive Resume when:

• You need dedicated capabilities in the Workplace & Productivity domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Resume and cover-letter document management, Resume and letter imports, PDF, Word, Markdown, and JSON exports.

Explore Reactive Resume Details

Feature & Specification Comparison

Specification	R Resume Workplace & Productivity	Reactive Resume Workplace & Productivity
Summary
Category & Scope	Workplace & Productivity	Workplace & Productivity
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "resume": {
      "command": "npx",
      "args": [
        "-y",
        "@theluckystrike/mcp-resume"
      ]
    }
  }
}

{
  "mcpServers": {
    "reactive-resume-2": {
      "url": "https://api.star-history.com/chart?repos=reactive-resume/reactive-resume&type=date&theme=dark&legend=top-left"
    }
  }
}

Related MCP Server Comparisons