Labsco
paladini logo

mcp-me

โ˜… 11

from paladini

Your AI assistants don't know who you are. mcp-me fixes that: a local MCP server that gives any AI a full picture of who you are

๐Ÿ”ฅ๐Ÿ”ฅโœ“ VerifiedFreeAdvanced setup

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.

You: "Write me a cover letter for this job"
AI:  (reads your me://career, me://skills, me://projects)
     "Based on your 5 years at Acme Corp, your TypeScript expertise,
      and your open-source work on mcp-me..."

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

Configure Your AI Assistant

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "me": {
      "command": "npx",
      "args": ["mcp-me", "serve", "/absolute/path/to/my-profile"]
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project root:

{
  "mcpServers": {
    "me": {
      "command": "npx",
      "args": ["mcp-me", "serve", "/absolute/path/to/my-profile"]
    }
  }
}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in your project root (or in your User Settings for global access):

{
  "servers": {
    "me": {
      "command": "npx",
      "args": ["mcp-me", "serve", "/absolute/path/to/my-profile"]
    }
  }
}

Tip: To enable it globally (all workspaces), open VS Code Settings (Ctrl+Shift+P โ†’ "Preferences: Open User Settings (JSON)") and add the mcp key there instead.

Claude Desktop

Add to your Claude Desktop config:

{
  "mcpServers": {
    "me": {
      "command": "npx",
      "args": ["mcp-me", "serve", "/absolute/path/to/my-profile"]
    }
  }
}

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.

FileWorks with
AGENTS.md (project root)Windsurf (Cascade), OpenAI Codex, Cline, and others
.github/copilot-instructions.mdGitHub Copilot (VS Code + GitHub.com)

Quick setup:

# AGENTS.md โ€” for Windsurf, Cline, Codex, etc.
cp "$(npm root -g)/mcp-me/templates/AGENTS.md" ./AGENTS.md

# GitHub Copilot
mkdir -p .github
cp "$(npm root -g)/mcp-me/templates/.github/copilot-instructions.md" .github/copilot-instructions.md

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:

FileDescription
identity.yamlName, bio, location, languages, contact info
career.yamlWork experience, education, certifications
skills.yamlTechnical and soft skills with proficiency levels
interests.yamlHobbies, music, books, movies, food preferences
personality.yamlValues, traits, MBTI, strengths
goals.yamlShort, medium, and long-term goals
projects.yamlPersonal and open-source projects
faq.yamlCustom Q&A pairs about yourself

See Schema Reference for full documentation.

MCP Interface

Resources

Static profile data exposed as MCP resources:

  • me://identity โ€” Personal identity and contact
  • me://career โ€” Professional history
  • me://skills โ€” Skills and proficiencies
  • me://interests โ€” Hobbies and preferences
  • me://personality โ€” Personality traits and values
  • me://goals โ€” Personal and professional goals
  • me://projects โ€” Portfolio and projects
  • me://faq โ€” Frequently asked questions

Tools

  • ask_about_me โ€” Free-form question about the user
  • search_profile โ€” Keyword search across all profile data

Prompts

  • introduce_me โ€” Generate a 2-paragraph introduction
  • summarize_career โ€” Summarize career trajectory
  • technical_profile โ€” Describe technical skills and stack
  • collaboration_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.

CategoryFlagSourceData
Code--github <user>GitHub APIRepos, languages, stars, profile
Code--gitlab <user>GitLab APIProjects, topics, profile
Code--bitbucket <user>Bitbucket APIRepos, languages
Code--huggingface <user>Hugging Face APIModels, datasets, spaces
Code--kaggle <user>Kaggle APICompetitions, datasets, medals
Code--codeberg <user>Gitea APIRepos, languages
Writing--devto <user>DEV.to APIArticles, tags, reactions
Writing--medium <user>Medium RSSArticles, categories, article text
Writing--blogger-backup <xml>Blogger XML exportImported posts from a local backup, filtered by author if needed
Writing--hashnode <user>Hashnode GraphQLBlog posts, tags
Writing--substack <user>Substack RSSNewsletter posts, article text
Writing--wordpress <site>WordPress APIBlog posts, categories, tags
Writing--openlibrary <user>Open Library APIBooks authored
Writing--orcid <id>ORCID APIAcademic publications
Writing--semanticscholar <id>S2 APIResearch papers, citations
Writing--youtube <channel>YouTube RSSVideos, channel info
Community--stackoverflow <id>Stack Exchange APITop tags, reputation, badges
Community--hackernews <user>HN Firebase APIKarma, submissions
Community--mastodon <user@host>Mastodon APIPosts, hashtags, bio
Community--bluesky <handle>AT Protocol APIPosts, followers
Community--reddit <user>Reddit JSON APIKarma, bio
Community--producthunt <user>ProductHunt GraphQLLaunched products, upvotes
Community--threads <user>Threads APIBio, follower stats
Packages--npm <user>npm RegistryPublished packages
Packages--pypi <pkgs>PyPI JSON APIPackage metadata
Packages--crates <user>Crates.io APIRust crates
Packages--dockerhub <user>Docker Hub APIContainer images
Activity--wakatime <user>WakaTime APICoding time, languages, editors

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:

# Import all posts from a Blogger export
mcp-me generate ~/my-profile --blogger-backup ~/Downloads/blog-2026-03-24.xml

# Import only posts written by specific authors/emails
mcp-me generate ~/my-profile --blogger-backup "~/Downloads/blog.xml::fernandopalad@gmail.com,fnpaladini@gmail.com,Fernando Paladini"

How to get the export file:

  1. Open Blogger and choose your blog.
  2. Go to Settings.
  3. In Manage blog, click Back up content.
  4. Download the XML file.
  5. 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.

PluginDescriptionAuth
GitHubLive repos, activity, languagesOptional token
SpotifyNow playing, top artists, playlistsOAuth required
LinkedInProfessional history from exportLocal JSON file
WakaTimeLive coding stats, languagesOptional API key
DEV.toLive articles, reactionsOptional API key
BlueskyLive posts, profile, followersNone
Hacker NewsLive stories, karmaNone
RedditLive karma, postsNone
GitLabLive projects, activity, MRsOptional token
MastodonLive toots, profile, engagementNone
YouTubeLive videos, channel statsOptional API key
Last.fmNow playing, top artists, scrobblesOptional API key
SteamCurrently playing, game libraryOptional API key

Enable plugins in .mcp-me.yaml:

plugins:
  github:
    enabled: true
    username: "your-username"
  spotify:
    enabled: true
    client_id_env: "SPOTIFY_CLIENT_ID"
    client_secret_env: "SPOTIFY_CLIENT_SECRET"
    refresh_token_env: "SPOTIFY_REFRESH_TOKEN"

Community plugins are installed from npm (mcp-me-plugin-*) and auto-discovered. See the Plugin Creation Guide.

Generators vs Plugins

GeneratorsPlugins
Run whenmcp-me generate (once)mcp-me serve (continuously)
OutputStatic YAML filesLive MCP resources/tools
AuthAlmost never neededSometimes (OAuth)
Example"Repos I had in March""Repos I have right now"
ExtendAdd src/generators/*.tsAdd src/plugins/*/

CLI Reference

# Auto-generate profile from multiple data sources
mcp-me generate <dir> --github <user> [--devto <user>] [--stackoverflow <id>] ...

# Initialize with blank YAML templates
mcp-me init <directory>

# Validate profile YAML files
mcp-me validate <directory>

# Start the MCP server
mcp-me serve <directory>

# Scaffold a new generator or plugin (for contributors)
mcp-me create generator <name> [--category <category>]
mcp-me create plugin <name>

Development

# Clone the repo
git clone https://github.com/paladini/mcp-me.git
cd mcp-me

# Install dependencies
npm install

# Run tests
npm test

# Build
npm run build

# Run in dev mode
npm run dev