
Kenmet
io.github.Magic-ResumePublished by GitHub account Magic-Resumev1.0.2Updated Nov 4, 2026
Read and edit Kenmet (formerly Magic Resume) resumes from any MCP client with safe JSON patches.
Overview
Local stdio MCP server that lets an assistant read Kenmet (formerly Magic Resume) resumes and apply schema-aware JSON patches through the Kenmet API.
- What you can do
- Read resumes stored in a Kenmet account through the Kenmet API
- Apply schema-aware JSON patches to edit resume content
- Run as a local stdio server or as a CLI executable named magic-resume
- Configure the API endpoint and personal access token from the command line
- When to use it
- Useful when you keep resumes in Kenmet and want an assistant to review or update them with structured, schema-checked edits instead of manual copy-paste in the editor.
- Requirements
- Runs locally as an npm package via npx (Node.js required) on desktop. Needs a compatible Kenmet API URL and a personal access token, set through the CLI config command. No environment variables or headers are declared in the manifest.
Installation
In SourceWeft
- Open Kenmet in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@magic-resume-kit/mcp
Local stdio MCP server and CLI for reading resumes and applying schema-aware patches through the Kenmet (formerly Magic Resume) API. It uses personal access tokens and requires a compatible API; it does not read the local editor's IndexedDB.
The executable remains magic-resume. Configure your MCP client to run npx with arguments -y, @magic-resume-kit/mcp, mcp. Use a real PAT only in your local setup, never in committed files. Schema and registry logic is bundled into the executable, avoiding React and PDF runtime dependencies for CLI users. MIT licensed.
Public distribution
Install @magic-resume-kit/mcp from the public npm registry. No GitHub Packages token or private registry configuration is required. The package source and release workflow live in Magic Resume Kit.
See the consumer integration guide for host requirements and the release guide for versioning and publication.
Source: packages/mcp/README.md at commit 148cd7a
Tools
0Version history
1- v1.0.2LatestNov 4, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts