Integrate Reactive Resume's MCP tools with DeepSeek Harness, enabling AI to directly read, modify, and lock users' online resumes and job applications.
- Language
- TypeScript
- License
- MIT
- Branch
- main
Install
$ dsh plugin --profile web add dsh-plugin-reactive-resumeRun the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial
Install via your agent
Install the DeepSeek Harness plugin amruthpillai/reactive-resume/packages/dsh-plugin for me: review the repository at https://github.com/amruthpillai/reactive-resume first, then run the install command and verify the plugin loads successfully.
Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.
One-Line Positioning
Integrate the MCP toolset of the online resume service Reactive Resume into DeepSeek Harness, enabling AI to read, modify, lock, and track user resumes and job applications like operating files. Includes a system prompt tutorial that teaches the model how to correctly write resume data, avoiding common patch path errors.
Core Capabilities
- Bridge Reactive Resume's MCP endpoint via streamable-http, exposing 28+ resume and job application tools to the model
- Inject a dedicated system prompt section that standardizes the model's resume editing process (list IDs first, read by ID, RFC 6902 patch, UUID-keyed entries, lock state handling)
- Read and forward user API Key, defaulting to the official hosted address
https://rxresu.me, also supports self-hosted instances - When API Key is not configured, only print warning without mounting tools, ensuring profile can still start
- Customize tool namespace at the plugin layer (
serverName) to avoid tool name conflicts when multiple Reactive Resume instances are connected
Technical Implementation
- Language: TypeScript (ESM, TypeScript 7)
- Key Dependencies:
@deepseek-ai/cordis(plugin host framework),@deepseek-ai/dsh-mcp-client(MCP bridging),@deepseek-ai/dsh-system-prompt(system prompt injection),@deepseek-ai/schemastery(config schema validation) - Architecture Pattern: Cordis bundle patch declarative injection —
cordis.patch.ymlinserts a linereactive-resumeat installation, the pluginapply(ctx, config)hook callsctx.plugin()to mount the MCP client when Harness starts, and appends prompts viactx.systemPrompt.section() - Entry File:
src/index.ts(applyfunction +Configschema +name/injectexports)
Use Cases
Users already managing online resumes with Reactive Resume who want DeepSeek Harness conversations to directly read, modify, batch update resumes or job applications. The pain point is: manually editing resume field names and copying work experience descriptions is tedious, and letting the model directly operate on data risks UUID guessing errors and lock state pitfalls — this plugin delivers both tools and operation specifications to the model.
Prerequisites and Compatibility
| Dependency | Minimum Version | Description |
|---|---|---|
| Node.js | ^22.19.0 || >=24.0.0 | From package.json#engines |
| @deepseek-ai/cordis | ^4.0.1 | Host framework, peerDependency |
| @deepseek-ai/dsh-mcp-client | ^0.1.0-rc.6 | MCP bridge client |
| @deepseek-ai/dsh-system-prompt | ^0.1.0-rc.6 | System prompt injection interface |
| @deepseek-ai/schemastery | ^3.18.1 | Config schema validation |
| Platform | Cross-platform | No native module dependencies |
| Native modules | None | Pure JS implementation |
Installation
dsh plugin --profile web add github:amruthpillai/reactive-resume/packages/dsh-plugin
Configuration Options
| Config | Type | Description | Default |
|---|---|---|---|
apiKey | string | API Key from <url>/dashboard/settings/api-keys; empty string means do not mount tools, just print warning | '' |
url | string | Root address of Reactive Resume instance; change to your own address for self-hosting | https://rxresu.me |
serverName | string | Tool namespace prefix, tools will appear as mcp__<serverName>__<toolName> on the model side; only letters, numbers, underscores, hyphens allowed, max 32 characters | resume |
toolCallTimeoutMs | number | Single tool call timeout (ms) | 60000 |
FAQ
Q: Do I need to configure apiKey immediately after installation?
A: No. When the apply function detects an empty apiKey, it only prints a warning and returns directly without calling ctx.plugin(). So without configuration, the profile can still start normally, and the model won't see Reactive Resume tools.
Q: Can I self-host Reactive Resume and connect it?
A: Yes. Change the url configuration to your self-hosted instance address (e.g., http://localhost:3000), the plugin will automatically strip trailing slashes and append the /mcp endpoint. Remember to also generate an API Key on the self-hosted instance.
Q: Can I expose only some tools instead of all for AI use?
A: No. Harness's ctx.tools.restrict() can only be called in agent context, while the plugin apply receives plugin-level context, so toolset trimming is not currently possible — all tools published by Reactive Resume will be exposed to the model.
Q: What is the serverName field for? What happens if I change it?
A: It's the tool namespace prefix; the actual tool name the model sees is mcp__<serverName>__<rawName>. The default is resume. If you want to connect both official and self-hosted instances simultaneously, change their serverName to different values (e.g., resume-hosted / resume-self) to avoid name conflicts.
Q: What does the plugin write to the system prompt?
A: It appends a "Reactive Resume" section via ctx.systemPrompt.section() covering: use list_resumes before edit_resume first, then read_resume, use RFC 6902 JSON Patch instead of overwrite, section entries are object arrays with UUID ids, locked resumes must be unlock_resume first, deletion actions require explicit user authorization, etc.
Q: What happens when a tool call times out?
A: Default single call timeout is 60 seconds (toolCallTimeoutMs: 60000), timeout is handled by dsh-mcp-client. If your network or resumes are particularly large, you can increase this value in your profile's cordis.patch.yml.
Difficulty Level
Beginner — only one required configuration (apiKey), all others have defaults. Regular users can use it once they get an API Key.
Known Issues and Limitations
- Toolset cannot be trimmed at the plugin layer; all tools published by Reactive Resume will be exposed to the model (src/index.ts:23-30)
- When apiKey is not configured, only warn without mounting, but there's no switch to disable warning messages (src/index.ts:44)
serverNamehas a 32-character limit and only allows[A-Za-z0-9_-]; exceeding or containing illegal characters will throw errors during schema validation (src/config.ts:4 / src/config.ts:28-32)- Plugin directly uses
failOnStartupError: trueso MCP startup failures bubble up to the host; network fluctuations during startup can cause profile startup failures (src/index.ts:56)
Reactive Resume
Reactive Resume is a free and open-source resume builder that simplifies the process of creating, updating, and sharing your resume.
Reactive Resume makes building resumes straightforward. Pick a template, fill in your details, and export to PDF—no account required for basic use. For those who want more control, the entire application can be self-hosted on your own infrastructure.
Built with privacy as a core principle, Reactive Resume gives you complete ownership of your data. The codebase is fully open-source under the MIT license, with no tracking, no ads, and no hidden costs.
Sponsors
Reactive Resume stays free, open-source, and independent because companies choose to support the work behind it. Thank you to every sponsor who helps fund hosting, maintenance, and continued development for the community.
Atlas Cloud supports Reactive Resume as a project sponsor. Atlas Cloud provides a unified AI platform for developers, with access to hundreds of models for chat, image generation, video generation, media processing, and GPU cloud workloads through one API key, one endpoint, and one billing account.
If your company would like to sponsor Reactive Resume, email [email protected].
Features
Resume Building
- 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
Templates
- Professionally designed templates
- A4 and Letter size support
- Customizable colors, fonts, and spacing
- Structured Style Rules for section and text styling
Privacy & Control
- Self-host on your own infrastructure
- No tracking or analytics by default
- Full data export at any time
- Delete your data permanently with one click
Extras
- AI integration (OpenAI, Google Gemini, Anthropic Claude)
- Multi-language support
- Share resumes via unique links
- Import from JSON Resume format
- Dark mode support
- Passkey and two-factor authentication
Templates
Azurill |
Bronzor |
Chikorita |
Ditto |
Gengar |
Glalie |
Kakuna |
Lapras |
Leafish |
Onyx |
Pikachu |
Rhyhorn |
Ditgar |
Meowth |
Scizor |
Quick Start
The quickest way to run Reactive Resume locally:
# Clone the repository
git clone --depth=1 https://github.com/amruthpillai/reactive-resume.git
cd reactive-resume
# Start all services
docker compose up -d
# Access the app
open http://localhost:3000
For detailed setup instructions, environment configuration, and self-hosting guides, see the documentation.
Tech Stack
| 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 |
| Styling | Tailwind CSS |
| UI Components | Base UI + shadcn-style package |
| State Management | Zustand + TanStack Query |
Documentation
Comprehensive guides are available at docs.rxresu.me:
| Guide | Description |
|---|---|
| Getting Started | First-time setup and basic usage |
| Self-Hosting | Deploy on your own server |
| Development Setup | Local development environment |
| Project Architecture | Codebase structure and patterns |
| Exporting Your Resume | PDF and JSON export options |
Self-Hosting
Reactive Resume can be self-hosted using Docker. The stack includes:
- PostgreSQL — Database for storing user data and resumes
- SeaweedFS (optional) — S3-compatible storage for file uploads
From v5.1.0 onwards — PDF generation now runs entirely client-side via
@react-pdf/renderer. New deployments no longer require Browserless, Chromium, or any external print service as a dependency. ThePRINTER_*andBROWSERLESS_*environment variables are no longer read and can be removed from your.env.
Pull the latest image from Docker Hub or GitHub Container Registry:
# Docker Hub
docker pull amruthpillai/reactive-resume:latest
# GitHub Container Registry
docker pull ghcr.io/amruthpillai/reactive-resume:latest
See the self-hosting guide for complete instructions.
Support
Reactive Resume is and always will be free and open-source. If it has helped you land a job or saved you time, please consider supporting continued development:
Other ways to support:
- Star this repository
- Report reproducible bugs and suggest actionable features
- Help other users in GitHub Discussions
- Improve documentation
- Help with translations
Star History
Contributing
Contributions make open-source thrive. Whether fixing a typo or adding a feature, all contributions are welcome.
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
See the development setup guide for detailed instructions on how to set up the project locally.
Maintainers review the status: needs triage queue
weekly. Triaged bugs become status: confirmed; feature proposals become status: accepted; reports that need details become
status: needs info.
License
MIT — do whatever you want with it.
Read the usage guide →
Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.
Listing badge
[](https://deepseek-plugin.org/plugins/amruthpillai/reactive-resume/packages/dsh-plugin)Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.