
mcp-me
io.github.paladiniPublished by GitHub account paladiniv0.6.0Updated Oct 25, 2026
Expose your personal, professional, educational, and social profile to any AI assistant via MCP.
Overview
A local MCP server that exposes a personal profile stored in YAML files, letting an AI assistant answer questions about your career, skills, projects and goals.
- What you can do
- Answer free-form questions about the user from the stored profile and search all profile data by keyword, exposed as the ask_about_me and search_profile tools and as me:// resources for identity, career, skills, interests, personality, goals, projects and FAQ. Run built-in prompts that draft an introduction, summarize a career, describe a technical profile or assess collaboration fit. Populate the profile from public sources with a generate command covering many services such as GitHub, DEV.to, Bluesky, Stack Overflow and Last.fm. Optionally enable live plugins that fetch current data such as now-playing music, repositories or coding stats at query time.
- When to use it
- Useful when you repeatedly give assistants the same background about yourself and want a reusable, local profile they can consult, for example when drafting cover letters, introductions or project-fit assessments.
- Requirements
- Node.js 20 or later and a local install via npm or npx. A profile directory, defaulting to ~/.mcp-me, which can be overridden with the MCP_ME_PROFILE_DIR environment variable. Network access for the generate command and for live plugins; some plugins need OAuth or API keys configured in the profile config file.
Installation
In SourceWeft
- Open mcp-me 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
[Harness Score L1 (Documented): measures AI-assisted development harness maturity with harness-score] [mcp-me — Your Digital Identity Layer for AI]
mcp-me
Your AI assistants don't know who you are. Every time you start a conversation with Claude, Copilot, Cursor, or Windsurf, it's a blank slate — no context about your skills, your projects, your career, or what you care about.
mcp-me fixes that. It creates a structured personal profile that any AI assistant can read via the Model Context Protocol (MCP). Think of it as a digital identity layer for AI — your bio, career, skills, interests, projects, and more, always available to every AI tool you use.
Why mcp-me?
- AI that knows you — Your assistants remember your skills, career, projects, and personality across every conversation
- Auto-generated — Pull data from 329 registered generators (implemented across 44 generator source files) with one command
- Privacy-first — All data stays local in YAML files on your machine. Nothing is sent to any cloud.
- Real-time plugins — 13 live integrations (Spotify now playing, GitHub repos, Last.fm scrobbles) that AI queries on demand
- Extensible — Community-driven generators and plugins. Add a new data source in ~10 lines of code.
- Works everywhere — Claude Desktop, Cursor, Windsurf, Copilot, and any MCP-compatible AI assistant
Installation
Prerequisite: Node.js 20 or later. Verify with
node -v.
One-Click Install
Add mcp-me to your AI assistant in one click — no path configuration needed (profile defaults to ~/.mcp-me):
[Add mcp-me to Cursor] [Install mcp-me in VS Code]
Claude Desktop: Download the latest .mcpb release and double-click to install, or drag it into Claude Desktop → Settings → Extensions.
After installing, initialize your profile:
npm (recommended)
This makes the mcp-me command available everywhere on your system. No need to clone any repository — npm downloads the package for you.
Alternative — run without installing (via npx):
npx downloads the package temporarily and runs it. Useful for trying mcp-me once, but slower on repeated use since it re-downloads each time.
Profile location: Commands default to
~/.mcp-me. Override withMCP_ME_PROFILE_DIRor pass an explicit path:mcp-me serve ~/my-profile.
Quick Start
Your .mcp-me.yaml config file:
CLI flags also work:
mcp-me generate --github octocat --devto myuser
All commands work with npx (zero install) or with mcp-me directly if installed globally. The generate command pulls your data from public APIs and auto-populates profile YAML files — no API keys needed for most sources.
Profile directory structure
Configure Your AI Assistant
One-Click (Cursor & VS Code)
Use the one-click install badges above. After installing, run mcp-me init to create your profile.
Cursor Plugin (Open Plugins)
mcp-me ships as a full Open Plugins plugin for Cursor. Install from cursor.directory or clone the repo — the plugin auto-detects all components:
Validate the plugin structure: npm run validate:open-plugin
Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
Cursor (manual)
Add to .cursor/mcp.json in your project root:
VS Code (GitHub Copilot)
Add to .vscode/mcp.json in your project root (or in your User Settings for global access):
Tip: To enable it globally (all workspaces), open VS Code Settings (
Ctrl+Shift+P→ "Preferences: Open User Settings (JSON)") and add themcpkey there instead.
Claude Desktop
Option A — Desktop Extension (.mcpb, recommended):
- Download
mcp-me.mcpbfrom GitHub Releases - Double-click the file, or drag it into Claude Desktop → Settings → Extensions
- Set your profile directory when prompted (default:
~/.mcp-me) - Run
mcp-me initif you haven't created a profile yet
Option B — Manual config:
Add to your Claude Desktop config:
Agent Instruction Files
AI agents read special Markdown files in your project to understand how they should behave. Pair them with mcp-me so that every AI session automatically consults your profile — no more repeating your stack, career, or preferences in every conversation.
Quick setup:
Both templates are included with mcp-me and tell the AI to call ask_about_me whenever context about you would improve the response.
See the Agent Instructions Guide for examples, global setup, and tips on combining with project-specific rules.
Profile Schema
Your profile is a collection of YAML files:
See Schema Reference for full documentation.
MCP Interface
Resources
Static profile data exposed as MCP resources:
me://identity— Personal identity and contactme://career— Professional historyme://skills— Skills and proficienciesme://interests— Hobbies and preferencesme://personality— Personality traits and valuesme://goals— Personal and professional goalsme://projects— Portfolio and projectsme://faq— Frequently asked questions
Tools
ask_about_me— Free-form question about the usersearch_profile— Keyword search across all profile data
Prompts
introduce_me— Generate a 2-paragraph introductionsummarize_career— Summarize career trajectorytechnical_profile— Describe technical skills and stackcollaboration_fit— Evaluate fit for a project
Generators (selected examples)
Generators run during mcp-me generate to auto-populate your profile from public APIs or user-provided exports. No API keys needed for most sources.
Current counts:
- Registered generators: 329
- Generator source files: 44 single-generator files + 15 batch files (
src/generators/)
The table below is a curated list of commonly used generators. The complete source of truth is
src/generators/index.ts.
Blogger XML Backup
--blogger-backup imports written content from a Blogger XML export file on disk. It is designed for archived or multi-author blogs where you want to recover your posts even if the site is old, partially offline, or not easily queryable through a public API.
By default it imports all post entries from the file. If the backup contains multiple authors, append ::author1,author2,... after the file path to keep only posts whose author name or email matches one of those values.
Examples:
How to get the export file:
- Open Blogger and choose your blog.
- Go to
Settings. - In
Manage blog, clickBack up content. - Download the XML file.
- Pass that file path to
--blogger-backup.
The generator imports matching posts into projects.yaml with category: article, preserves post labels as tags, and adds summary FAQ entries about the archive.
| Activity | --letterboxd <user> | Letterboxd RSS | Films watched, ratings |
| Activity | --goodreads <user> | Goodreads RSS + author page | Read books, shelves, reviews, published books |
| Activity | --chess <user> | Chess.com API | Rating, stats |
| Activity | --lichess <user> | Lichess API | Rating, games |
| Activity | --codewars <user> | Codewars API | Rank, honor, languages |
| Activity | --leetcode <user> | LeetCode GraphQL | Problems solved, contests |
| Activity | --lastfm <user> | Last.fm API | Listening history, top artists |
| Activity | --steam <id> | Steam API | Games, playtime |
| Activity | --twitch <user> | Twitch API | Stream info |
| Activity | --dribbble <user> | Dribbble | Design shots, portfolio |
| Activity | --unsplash <user> | Unsplash API | Photos, downloads, collections |
| Activity | --exercism <user> | Exercism API | Language tracks, exercises |
| Activity | --hackerrank <user> | HackerRank API | Badges, challenges solved |
| Activity | --anilist <user> | AniList GraphQL | Anime/manga stats, genres |
| Identity | --gravatar <email> | Gravatar API | Bio, linked accounts, photo |
| Identity | --keybase <user> | Keybase API | Verified identity proofs |
Want to add a new data source? See the Generator Creation Guide.
Plugins (13 live integrations)
Plugins run during mcp-me serve and provide real-time data to AI assistants on every query.
Enable plugins in .mcp-me.yaml:
Community plugins are installed from npm (mcp-me-plugin-*) and auto-discovered. See the Plugin Creation Guide.
Generators vs Plugins
CLI Reference
Profile location: Defaults to
~/.mcp-me. Override withMCP_ME_PROFILE_DIRor pass an explicit[directory]argument.
Development
FAQ
What is MCP (Model Context Protocol)? MCP is an open standard by Anthropic that connects AI assistants to external data sources. mcp-me uses MCP to let AI assistants read your personal profile data.
Do I need API keys?
Most generators use public APIs with no auth needed. Some (Strava, Spotify) require tokens — see the .mcp-me.yaml comments for details.
Can I use this with Claude Desktop / VS Code / Cursor / Windsurf? Yes! Any MCP-compatible AI assistant works. See the Configure Your AI Assistant section.
How do I make AI agents use my profile automatically?
Drop an AGENTS.md (for Windsurf, Cline, Codex) or .github/copilot-instructions.md (for GitHub Copilot) into your project. Templates are included — see the Agent Instructions Guide.
How do I add a new data source?
Run mcp-me create generator myservice to scaffold a new generator, or see the Generator Creation Guide.
Is my data stored anywhere? No. All data stays local in your YAML files. The MCP server reads from disk — nothing is sent to any cloud.
How many generators are there? Currently 329 registered generators, implemented across 44 generator source files plus 15 batch files.
Contributing
We welcome contributions! Whether it's a new plugin, a bug fix, or documentation improvements — see CONTRIBUTING.md for guidelines.
Maintainers: see Publishing Guide for release and distribution instructions.
License
Source: README.md at commit 34f85ac
Tools
0Version history
1- v0.6.0LatestSep 16, 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