personal-context
Aggregates your digital footprint (GitHub, blogs, resume) into a single AI-readable profile and exposes it via MCP tools so AI agents can query your context live.
README
personal-context
Turn your digital footprint into an AI-readable profile. GitHub + Blogs + Resume + Notes -> one context source for every AI agent.
<p align="center"> <img src="docs/demo.gif" alt="personal-context CLI demo" width="760" /> </p>
[!NOTE] Work in progress — something crazy on the way. ✦
Documentation: https://ayush7614.github.io/personal-context/
Current AI tools forget who you are. You keep re-explaining your work, skills,
projects, blogs, and open-source contributions. personal-context aggregates
all of it from your real sources and outputs it as a single profile you can
print, share, or feed to any AI tool (Cursor, Claude Code, Codex, Gemini CLI).
$ npx personal-context all
Ayush Kumar
DevRel · AI Agents · Open Source · AI Security
Current Role:
Lead Developer Relations Engineer @ NodeShift AI Cloud
Contact:
Email: ayushknj3@gmail.com
GitHub: https://github.com/Ayush7614
Recent Blogs:
- AI Agents Masterclass — Full Visual Guide
- Harness Engineering — Full Visual Guide
...
GitHub:
Contributions: 1250
Repositories: 35
...
Quick start
# 1. Scaffold a config in the current folder
npx personal-context init
# 2. Edit personal.yaml with your details + source handles
# 3. See your full profile
npx personal-context all
# 4. Generate AI-readable files (context.md, profile.json, llms.txt)
npx personal-context build
Commands
| Command | Description |
|---|---|
init |
Create a starter personal.yaml |
teaser (wip) |
Animated "something crazy on the way" splash |
all |
Full profile overview (the single-command output) |
github |
GitHub stats + latest contributions |
blogs [--limit N] |
Recent posts across all RSS feeds |
linkedin |
Role + experience timeline |
opensource (oss) |
Open-source contributions |
build [--out dir] |
Write context.md, profile.json, llms.txt |
summary |
One-paragraph AI brief |
Every read command supports --json for piping into other tools.
Configuration
Everything is driven by a single personal.yaml (see personal.yaml
for a full reference). Static facts (name, role, skills, projects) live in the
file; live data is pulled from the sources you configure:
| Information | Source |
|---|---|
| GitHub contributions, PRs, repos | GitHub REST + GraphQL API |
| Latest blogs | RSS feeds (Medium, Hashnode, Dev.to) |
| Experience timeline | personal.yaml + LinkedIn export (JSON) |
| Resume skills / summary | Resume JSON or PDF |
Set GITHUB_TOKEN (see .env.example) to unlock contribution
counts and higher rate limits.
MCP server
personal-context also ships an MCP server so
any AI agent (Cursor, Claude Code, Codex, etc.) can query your context live.
Add it to your MCP client config (e.g. Cursor's ~/.cursor/mcp.json):
{
"mcpServers": {
"personal-context": {
"command": "npx",
"args": ["-y", "personal-context-mcp"],
"env": {
"PERSONAL_CONTEXT_CONFIG": "/absolute/path/to/personal.yaml",
"GITHUB_TOKEN": "optional-token"
}
}
}
}
Then your agent can call:
| Tool | Returns |
|---|---|
get_profile |
The full profile object |
get_summary |
One-paragraph AI brief |
get_recent_blogs { limit } |
Recent posts across feeds |
get_github_stats |
Contributions, PRs, repos, top repos |
get_projects |
Projects you build/ship |
get_open_source |
Open-source contributions |
get_contact_info |
Email, website, socials |
get_learning_history |
What you're learning + skills |
PERSONAL_CONTEXT_CONFIG points the server at your personal.yaml regardless of
the directory the client launches it from.
Architecture
A pnpm monorepo with a shared core so the CLI, the MCP server, and your portfolio all consume the same profile data.
personal-context/
├── packages/
│ ├── core/ # sources + aggregation + renderers (Profile, context.md, llms.txt)
│ ├── cli/ # the `personal-context` command
│ └── mcp/ # the `personal-context-mcp` MCP server
└── personal.yaml
Roadmap
- v1 — Core + CLI (GitHub, blogs, LinkedIn, resume, generated profiles) ✅
- v2 — MCP server (
get_profile,get_recent_blogs,get_github_stats, ...) ✅ + portfoliocontext.json/llms.txtendpoints (in progress) - v3 — "Ask My Portfolio" chat + auto-learning timeline
- v4 — AI personal brief + scheduled refresh
License
MIT © Ayush Kumar
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。