Ryan/Reactive-Resume
1
0
Fork 0
mirror of https://github.com/AmruthPillai/Reactive-Resume.git synced 2026-07-12 14:05:08 +10:00
Code Issues Packages Projects Releases Wiki Activity

Fix MCP tool names for Claude Desktop incompatibility (#2885)

Browse Source 
* fixes #2884, rename tool names for claude to work

* update dependencies
This commit is contained in:
Amruth Pillai
2026-04-09 15:03:18 +02:00
committed by GitHub
parent 85e0b0a96d
commit bea8ff1beb
10 changed files with 543 additions and 227 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guides/using-the-mcp-server.mdx
+26 -18
View File
@@ -207,25 +207,29 @@ If you're running a self-hosted Reactive Resume instance, replace `https://rxres
## Available Tools
Tool names use a hierarchical `reactive_resume.*` prefix ([SEP-986](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/986) style) so they stay distinct when multiple MCP servers are enabled in the same client.
Tool names use a `reactive_resume_` prefix so they stay distinct when multiple MCP servers are enabled in the same client.
| Tool | Description |
| --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| `reactive_resume.list_resumes` | List all resumes with IDs, names, tags, and status. Supports filtering by tags and sorting by last updated, creation date, or name |
| `reactive_resume.get_resume` | Get the full data of a specific resume by ID |
| `reactive_resume.create_resume` | Create a new, empty resume with a name and slug. Optionally pre-fill with sample data |
| `reactive_resume.duplicate_resume` | Create a copy of an existing resume with a new name and slug |
| `reactive_resume.patch_resume` | Apply JSON Patch (RFC 6902) operations to modify a resume's data |
| `reactive_resume.delete_resume` | Permanently delete a resume and all associated files. **Irreversible** |
| `reactive_resume.lock_resume` | Lock a resume to prevent edits, patches, and deletion |
| `reactive_resume.unlock_resume` | Unlock a previously locked resume to re-enable editing |
| `reactive_resume.export_resume_pdf` | Generate a PDF from the resume and return a download URL |
| `reactive_resume.get_resume_screenshot` | Get a visual preview of the resume's first page as a WebP image URL |
| `reactive_resume.get_resume_statistics` | Get view and download statistics for a resume |
| `reactive_resume_list_resumes` | List all resumes with IDs, names, tags, and status. Supports filtering by tags and sorting by last updated, creation date, or name |
| `reactive_resume_list_resume_tags` | List every distinct tag in use across your resumes (sorted) |
| `reactive_resume_get_resume` | Get the full data of a specific resume by ID |
| `reactive_resume_get_resume_analysis` | Get the latest saved AI analysis for a resume (from the web app), if any |
| `reactive_resume_create_resume` | Create a new, empty resume with a name and slug. Optionally pre-fill with sample data |
| `reactive_resume_import_resume` | Create a resume from a full ResumeData JSON export (random name/slug). Large files may exceed client limits |
| `reactive_resume_duplicate_resume` | Create a copy of an existing resume with a new name and slug |
| `reactive_resume_patch_resume` | Apply JSON Patch (RFC 6902) operations to modify a resume's data |
| `reactive_resume_update_resume` | Update metadata only: name, slug, tags, `isPublic`. Returns canonical share URL; passwords are not managed via MCP |
| `reactive_resume_delete_resume` | Permanently delete a resume and all associated files. **Irreversible** |
| `reactive_resume_lock_resume` | Lock a resume to prevent edits, patches, and deletion |
| `reactive_resume_unlock_resume` | Unlock a previously locked resume to re-enable editing |
| `reactive_resume_export_resume_pdf` | Generate a PDF from the resume and return a download URL |
| `reactive_resume_get_resume_screenshot` | Get a visual preview of the resume's first page as a WebP image URL |
| `reactive_resume_get_resume_statistics` | Get view and download statistics for a resume |
### Breaking change (tool names)
Older clients may refer to unprefixed names (`list_resumes`, `get_resume`, …). Those names are no longer used; update automations and saved prompts to the `reactive_resume.*` names above.
Older clients may refer to unprefixed names (`list_resumes`, `get_resume`, …) or dot-separated names (`reactive_resume.list_resumes`, …). Those names are no longer used; update automations and saved prompts to the `reactive_resume_*` names above.
## Available Resources
@@ -235,12 +239,12 @@ Resources follow MCP conventions: **static** items appear in `resources/list`; *
| ------------------------------------- | --------------------------------------------------------------------------------------------- |
| `resources/list` | Static resources only — currently **`resume://_meta/schema`** (ResumeData JSON Schema) |
| `resources/templates/list` | **`resume://{id}`** — template for reading full resume JSON by ID (not enumerated per resume) |
| `reactive_resume.list_resumes` (tool) | **Primary way to discover resume IDs** — resumes are not listed as separate MCP resources |
| `reactive_resume_list_resumes` (tool) | **Primary way to discover resume IDs** — resumes are not listed as separate MCP resources |
| URI | Description |
| ----------------------- | ------------------------------------------------------------------------ |
| `resume://_meta/schema` | ResumeData JSON Schema — use for valid JSON Patch paths and value types |
| `resume://{id}` | Full resume data as JSON — use an ID from `reactive_resume.list_resumes` |
| `resume://{id}` | Full resume data as JSON — use an ID from `reactive_resume_list_resumes` |
### Breaking change (schema URI)
@@ -275,7 +279,10 @@ Once your MCP client is connected, you can use natural language to interact with
### Creating & Managing
- "Create a new resume called 'Frontend Engineer 2026'"
- "Import this exported ResumeData JSON as a new resume"
- "What tags do I use across my resumes?"
- "Duplicate my 'Software Engineer' resume for a product manager role"
- "Make my resume public and give me the share link"
- "Lock my finalized resume so it can't be accidentally edited"
- "Delete my old draft resume"
@@ -306,8 +313,9 @@ Once your MCP client is connected, you can use natural language to interact with
- "Tailor my resume for this job description: ..." (uses `tailor_resume`)
<Tip>
The AI will use `reactive_resume.get_resume` to inspect your current resume before making changes with
`reactive_resume.patch_resume`. This ensures the correct JSON paths are used.
The AI will use `reactive_resume_get_resume` to inspect your current resume before making changes with
`reactive_resume_patch_resume`. This ensures the correct JSON paths are used. Use `reactive_resume_update_resume` for
name, slug, tags, and public visibility (not for section content).
</Tip>
## Troubleshooting
@@ -317,7 +325,7 @@ Once your MCP client is connected, you can use natural language to interact with
| "Unauthorized" with no login prompt | Your client may not support MCP OAuth discovery. Use API key mode (`x-api-key`) |
| OAuth login opens but fails redirect/callback | Confirm your client's MCP OAuth callback settings and retry the connection |
| "API error (401)" | Your API key is invalid or expired. Create a new one in **Settings → API Keys** |
| "API error (404)" | The resume ID doesn't exist. Use `reactive_resume.list_resumes` to find valid IDs |
| "API error (404)" | The resume ID doesn't exist. Use `reactive_resume_list_resumes` to find valid IDs |
| "API error (403)" | The resume is locked. Unlock it in the Reactive Resume dashboard |
| Connection refused | Check that the URL is correct and the instance is running |
| "ReferenceError: File is not defined" when using `mcp-remote` | You're running Node.js 18. `mcp-remote` requires **Node.js 20 or later** — upgrade with `nvm use 20` or `nvm alias default 20` |