Internals

​

Layout

packages/mcp/
├── src/
│   ├── cli.ts           # `magic-resume` CLI entrypoint (config get/set/print/clear)
│   ├── server.ts        # MCP server: tool registration, stdio transport
│   ├── resume-tools.ts  # business logic for every tool above
│   ├── config.ts        # ~/.magic-resume/mcp.json reader/writer
│   └── http.ts          # thin axios wrapper that sends the PAT
├── test/                # node --test suites
└── package.json         # type: "module", bin: magic-resume

​

Entry points

• CLI: bin: { "magic-resume": "./dist/cli.js" } in package.json. Subcommands: config set, config get, config print, config clear, and mcp (which boots the server).
• MCP server: magic-resume mcp boots server.ts, registers tools, attaches StdioServerTransport, and runs forever.

​

Config file

{
  "apiUrl": "https://api.magic-resume.cn/api",
  "pat": "mr_pat_xxx"
}

​

Tool registration

• A name and description
• A Zod-derived input schema (so the model gets typed parameter hints)
• A handler delegating to resume-tools.ts

​

Core API contract

​

Build and publish

pnpm --filter @magic-resume/mcp build      # tsc → dist/
pnpm --filter @magic-resume/mcp test       # node --test test/*.test.mjs
pnpm --filter @magic-resume/mcp lint       # tsc --noEmit

​

Adding a new tool

1. Add the handler to resume-tools.ts. Keep it pure and patch-based.
2. Register it in server.ts with a Zod input schema and a short description.
3. Add a node --test case in test/.
4. If the tool reads or mutates a new field, update get_resume_editing_guide so models know how to use it.