whoami-mcp
Exposes a person's structured professional profile as MCP tools, enabling Claude and other MCP clients to answer questions about that person based on real data.
README
whoami-mcp
A Model Context Protocol server that exposes a person's structured professional profile — experience, projects, skills, education, certifications — as MCP tools. Point Claude (or any MCP client) at it and it can answer questions about that person from real data instead of guesswork.
One package, three ways to use it:
- Library —
npm i whoami-mcp, build your own integration on the tools. - Local (stdio) —
npx whoami-mcpfor Claude Desktop. - Deployable (HTTP) — a stateless Streamable-HTTP server you can host (Docker-ready).
Install
One click — pick your client:
Or follow a per-client guide:
| Client | Guide |
|---|---|
| Cursor | installation/install-cursor.md |
| Claude Desktop | installation/install-claude-desktop.md |
| Claude Code | installation/install-claude-code.md |
| VS Code (Copilot) | installation/install-vscode.md |
| Windsurf | installation/install-windsurf.md |
| Remote / HTTP deploy | installation/install-http.md |
After install, point the server at your profile.
Contents
- Install
- Tools
- Chat (optional)
- Your profile
- Local (stdio) — Claude Desktop
- Deploy (Streamable HTTP)
- Build on the library
- Layout
- License
Tools
| Tool | Returns |
|---|---|
get_profile |
Name, role, company, location, bio, availability, preferred stack, links |
get_experience |
Work history: companies, roles, dates, descriptions, achievements |
get_projects |
Projects: tech stack, problem solved, your specific role, links |
get_skills |
Skills by category with proficiency levels |
get_education |
Education history + professional certifications |
Chat (optional)
Set a chat provider and the server gains an extra ask tool — it answers
free-form questions in the person's voice, grounded in the profile, instead of
just returning raw data. Off by default (the data tools work without it).
It speaks the OpenAI-compatible /chat/completions API, so any provider
works — set a base URL + model (+ key if needed):
| Provider | CHAT_BASE_URL |
CHAT_MODEL |
|---|---|---|
| OpenAI | https://api.openai.com/v1 |
gpt-4o-mini |
https://generativelanguage.googleapis.com/v1beta/openai |
gemini-2.0-flash |
|
| Ollama (local, no key) | http://localhost:11434/v1 |
llama3.2 |
| Groq | https://api.groq.com/openai/v1 |
llama-3.3-70b-versatile |
CHAT_BASE_URL=https://api.openai.com/v1 CHAT_API_KEY=sk-... CHAT_MODEL=gpt-4o-mini \
PROFILE_PATH=data/profile.json npm run start:http
Env: CHAT_BASE_URL, CHAT_MODEL (both required to enable), CHAT_API_KEY
(optional), CHAT_TEMPERATURE (default 0.4). See .env.example.
Your profile
Every server reads one profile JSON with six top-level keys: basic, experience, projects, skills, education, certifications. See data/profile.example.json for the exact shape.
cp data/profile.example.json data/profile.json # then edit
Point a server at it however suits your deploy (precedence top to bottom):
PROFILE_URL— fetch the JSON over HTTP (a GitHub gist, your hosted profile API, any endpoint)PROFILE_PATH— read this file./profile.json— default file in the working directory
Local (stdio) — Claude Desktop
{
"mcpServers": {
"whoami": {
"command": "npx",
"args": ["-y", "whoami-mcp", "whoami-stdio"],
"env": { "PROFILE_PATH": "/abs/path/to/your/profile.json" }
}
}
}
From a clone instead: npm install && npm run build, then point command/args at node /abs/path/to/dist/stdio.js.
Other clients: Cursor · Claude Code · VS Code · Windsurf.
Deploy (Streamable HTTP)
A long-running, stateless HTTP server — host it anywhere that runs a container.
docker compose up --build # serves MCP at http://localhost:8080/mcp
Without Docker:
npm install && npm run build
PROFILE_PATH=data/profile.json npm run start:http
Connect an MCP client to the endpoint:
{ "mcpServers": { "whoami": { "url": "http://localhost:8080/mcp" } } }
Health check: GET /health → {"status":"ok"}.
Full deploy + remote-client guide: installation/install-http.md.
Build on the library
npm i whoami-mcp
import { registerTools, type NormalizedProfile } from "whoami-mcp";
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
const server = new McpServer({ name: "whoami", version: "1.0.0" });
registerTools(server, profile); // profile: NormalizedProfile
whoami-mcp/http also exports createHttpHandler(profile, opts) for Next.js / fetch runtimes.
Layout
src/
index.ts library entry — TOOLS, registerTools, types
http.ts createHttpHandler (fetch/Next factory) → exported as whoami-mcp/http
tools.ts the five tool definitions
types.ts NormalizedProfile + tool types
register.ts registerTools(server, profile)
loadProfile.ts read PROFILE_PATH / ./profile.json
stdio.ts bin: whoami-stdio
http-server.ts bin: whoami-http (deployable, SDK StreamableHTTP)
npm install
npm run build
License
MIT — see LICENSE.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。