JSON Resume MCP Server

Most developer tooling work still happens through a UI a human drives. JSON Resume MCP server moves it into the conversation instead. Automates resume updates by analyzing coding projects using AI.

The short version

1. Check if you have an existing JSON Resume 2. Analyze your codebase to understand your technical skills and projects 3. Enhance your resume with details about your current project

• Resume Enhancement — Automatically analyzes your codebase and adds project details to your resume
• GitHub Integration — Fetches and updates your resume stored in GitHub Gists
• AI-Powered — Uses OpenAI to generate professional descriptions of your projects and skills
• TypeScript/Zod Validation — Ensures your resume follows the JSON Resume standard
• JSON Resume Ecosystem — Compatible with the JSON Resume registry

The tools it exposes

The server publishes 3 tools. What each one is for:

• Prerequisites — The Prerequisites tool exposed by this server
• Windsurf — The Windsurf tool exposed by this server
• Cursor — The Cursor tool exposed by this server

Getting it running

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: GITHUB_TOKEN, OPENAI_API_KEY, GITHUB_USERNAME. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• GitHub account with a personal access token (with gist scope) - OpenAI API key - Node.js 18+ - An IDE with MCP support (Windsurf or Cursor)

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. JSON Resume's toolset — Prerequisites, Windsurf, Cursor — is a fair guide to whether it matches your workflow. It is maintained by jsonresume; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.