Summary

Stop re-explaining your stack and your history in every new chat.

The distinction worth learning is generators versus plugins: generators write static YAML once, plugins answer live while the server runs. A cover letter comes out of the first; what you are listening to right now comes out of the second.

What it is

A local server over a folder of YAML files describing you — identity, career, skills, interests, personality, goals, projects and an FAQ. The server reads from disk; nothing is sent to a cloud.

What you get

Eight profile resources: me://identity, me://career, me://skills, me://interests, me://personality, me://goals, me://projects and me://faq
A free-form question about you, answered from the profile — ask_about_me
Keyword search across all profile data — search_profile
Four prompts: introduce_me, summarize_career, technical_profile and collaboration_fit
329 registered generators that populate the YAML from public APIs — GitHub, GitLab, DEV.to, Mastodon, Bluesky, ORCID, npm, PyPI, Last.fm, Steam and more — with no key needed for most
13 live plugins that answer at query time rather than from the last generate run, including Spotify now playing, GitHub activity and Last.fm scrobbles
Templates for AGENTS.md and .github/copilot-instructions.md that tell an agent to consult the profile on its own

Requirements

Node.js 20 or later. Install mcp-me from npm (version 0.6.0) and run mcp-me serve; the profile defaults to ~/.mcp-me and MCP_ME_PROFILE_DIR overrides it. Run mcp-me init once to create the YAML templates. Most generators need no key; Spotify requires OAuth, and GitHub, WakaTime, DEV.to and YouTube take an optional one.

Setup effort

One command — npm install -g mcp-me

MCP Me