@magic-resume-kit/* from npm.
This page is for contributors changing the MCP package itself or building a fork. The CLI and server share config.ts, and the server talks to the API through client.ts. The CLI handles one-shot config commands, while the MCP server is the process AI tools spawn.
How is the MCP package organized?
config.ts; the server talks to the API through client.ts. The CLI is for one-shot config commands; the MCP server is what AI tools spawn.
What are the CLI and MCP server entry points?
- CLI:
bin: { "magic-resume": "./dist/cli.js" }inpackage.json. Subcommands:config set,config print(PAT masked),config clear, andmcp(which boots the server). - MCP server:
magic-resume mcpbootsserver.ts, registers tools, attachesStdioServerTransport, and runs forever.
Where is the config file and what does it contain?
~/.magic-resume/mcp.json:
config.ts reads this lazily on first use. On Windows the path is %USERPROFILE%\.magic-resume\mcp.json.
How are MCP tools registered?
server.ts uses @modelcontextprotocol/sdk to register each tool with:
- A name and description
- A Zod-derived input schema (so the model gets typed parameter hints)
- A handler delegating to
resume-tools.ts
McpError with a stable error code so AI tools can react (e.g. retry on transient network failures, abort on validation errors).
What Core API endpoints does MCP use?
The MCP server is a client of the same NestJS Core API the web app talks to. Relevant endpoints:client.ts attaches Authorization: Bearer <pat> automatically. Unlike the web app, there is no Clerk involvement — PATs are a separate auth method the Core API understands.
How do I build and publish the MCP package?
publishConfig.access = "public" and uses pnpm’s workspace:* rewriting so the published package.json has real semver versions for @magic-resume-kit/resume-schema and @magic-resume-kit/resume-templates.
How do I add a new MCP tool?
- Add the handler to
resume-tools.ts. Keep it pure and patch-based. - Register it in
server.tswith a Zod input schema and a short description. - Add a
node --testcase intest/. - If the tool reads or mutates a new field, update
get_resume_editing_guideso models know how to use it.
