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

AI-generated 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.
Before you install
The profile holds personal data such as contact details, career history and interests, so anyone with access to the machine or the assistant can read it. The generate command sends your usernames to third-party public APIs, and plugins query external services at runtime. Some plugins require credentials such as Spotify OAuth values or API keys, which are referenced by environment variable names in the config file.

Installation

In SourceWeft

  1. Open mcp-me in the dashboard and add it to a workspace.
  2. 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.

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

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:

bash
mcp-me initmcp-me generate --github your-username

npm (recommended)

bash
npm install -g mcp-me

This makes the mcp-me command available everywhere on your system. No need to clone any repository — npm downloads the package for you.

bash
mcp-me --helpmcp-me initmcp-me generate --github your-usernamemcp-me serve

Alternative — run without installing (via npx):

bash
npx mcp-me --help

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 with MCP_ME_PROFILE_DIR or pass an explicit path: mcp-me serve ~/my-profile.

Quick Start

bash
# 1. Initialize your profile (creates YAML templates + .mcp-me.yaml in ~/.mcp-me)mcp-me init
# 2. Edit the config file — uncomment your sourcescode ~/.mcp-me/.mcp-me.yaml

Your .mcp-me.yaml config file:

yaml
generators:  github: your-username  devto: your-username  bluesky: handle.bsky.social  zodiac: aquarius
plugins:  github:    enabled: true    username: your-username
bash
# 3. Generate! Reads sources from .mcp-me.yaml automaticallymcp-me generate
# 4. Start the MCP servermcp-me serve

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

~/.mcp-me/             → Default profile location  .mcp-me.yaml        → Configuration (generators + plugins)  identity.yaml        → Your data (name, bio, contact)  skills.yaml          → Your data (languages, tools)  projects.yaml        → Your data (portfolio)  career.yaml          → Your data (experience)  interests.yaml       → Your data (hobbies, topics)  personality.yaml     → Your data (traits, values)  goals.yaml           → Your data (short/long-term)  faq.yaml             → Your data (Q&A pairs)

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:

ComponentLocationPurpose
MCP Servermcp.jsonZero-config npx -y mcp-me serve
Rulesrules/Always consult profile before answering
Skillsskills/Profile usage and setup guides
Agentsagents/Profile assistant and intro writer
Commandscommands//ask-about-me and /introduce-me
Hookshooks/hooks.jsonSession-start profile reminder
LSP.lsp.jsonYAML language server for profile files

Validate the plugin structure: npm run validate:open-plugin

Windsurf

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

json
{  "mcpServers": {    "me": {      "command": "npx",      "args": ["-y", "mcp-me", "serve"]    }  }}

Cursor (manual)

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

json
{  "mcpServers": {    "me": {      "command": "npx",      "args": ["-y", "mcp-me", "serve"]    }  }}

VS Code (GitHub Copilot)

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

json
{  "servers": {    "me": {      "command": "npx",      "args": ["-y", "mcp-me", "serve"]    }  }}

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

Option A — Desktop Extension (.mcpb, recommended):

  1. Download mcp-me.mcpb from GitHub Releases
  2. Double-click the file, or drag it into Claude Desktop → Settings → Extensions
  3. Set your profile directory when prompted (default: ~/.mcp-me)
  4. Run mcp-me init if you haven't created a profile yet

Option B — Manual config:

Add to your Claude Desktop config:

json
{  "mcpServers": {    "me": {      "command": "npx",      "args": ["-y", "mcp-me", "serve"]    }  }}

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:

bash
# AGENTS.md — for Windsurf, Cline, Codex, etc.cp "$(npm root -g)/mcp-me/templates/AGENTS.md" ./AGENTS.md
# GitHub Copilotmkdir -p .githubcp "$(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:

bash
# Import all posts from a Blogger exportmcp-me generate --blogger-backup ~/Downloads/blog-2026-03-24.xml
# Import only posts written by specific authors/emailsmcp-me generate --blogger-backup "~/Downloads/blog.xml::[email protected],[email protected],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:

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

bash
# Auto-generate profile from multiple data sourcesmcp-me generate [--directory] --github <user> [--devto <user>] [--stackoverflow <id>] ...
# Initialize with blank YAML templates (defaults to ~/.mcp-me)mcp-me init [directory]
# Validate profile YAML filesmcp-me validate [directory]
# Start the MCP server (defaults to ~/.mcp-me)mcp-me serve [directory]
# Scaffold a new generator or plugin (for contributors)mcp-me create generator <name> [--category <category>]mcp-me create plugin <name>

Profile location: Defaults to ~/.mcp-me. Override with MCP_ME_PROFILE_DIR or pass an explicit [directory] argument.

Development

bash
# Clone the repogit clone https://github.com/paladini/mcp-me.gitcd mcp-me
# Install dependenciesnpm install
# Run testsnpm test
# Buildnpm run build
# Run in dev modenpm run dev

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

MIT

Source: README.md at commit 34f85ac

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  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