personal-mcp-context
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@personal-mcp-contextshow my personal info"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Personal MCP Context Registry
A Model Context Protocol (MCP) Server to store and serve your personal context — identity, devices, servers, and projects — as structured Markdown files with a knowledge graph, accessible on-demand by AI Agents (Claude Desktop, Cursor, OpenCode, Antigravity AGY).
Why?
Instead of pasting all your personal info into every AI chat session (wasting tokens and context window), this server lets any MCP-compatible AI agent query only what it needs, when it needs it. Think of it as a personal knowledge base with graph traversal, fuzzy search, and an audit log.
Related MCP server: Lspace MCP Server
Features
🗂 Graph-backed Storage — Markdown files (
personal.md,devices.md,servers.md, etc.) linked via semantic relations inindex.json🔍 Fuzzy Search — Fast in-memory search across all context files via
Fuse.js🔗 Graph Traversal — Query related nodes at configurable depth
🛡 Safe Writes — Every write auto-backs up the existing file before overwriting; rollback on validation failure
📋 Audit Log — JSON-lines access log with auto-purge of entries older than 30 days
✅ Integrity Validator — Detects broken links, orphan nodes, and missing files
🐳 Docker-ready — Bind-mount your data from
~/context-dataon host, bound exclusively to127.0.0.1:3031🗂 Multi-namespace — Separate namespaces for
personal,work,project-xcontexts
Available MCP Tools
Tool | Description |
| List all nodes and links in the graph |
| Read full markdown content of a node |
| Fuzzy search across all context files |
| Traverse graph relations from a node |
| Create a new node with markdown content |
| Update existing node content (overwrite / append) |
| Soft-delete node (moves file to |
| Link two nodes with a named relation |
| Remove a link between two nodes |
| Run integrity check on graph & files |
| Full backup of namespace to |
| Read the audit access log |
Tech Stack
Layer | Technology |
Runtime | Node.js 20 + TypeScript |
Transport | Streamable HTTP ( |
Storage | Markdown files + JSON graph |
Search |
|
Auth | None (localhost only for MVP) |
Deployment | Docker Compose |
Quick Start
Prerequisites
Docker & Docker Compose installed
1. Clone & Create context data directory
git clone https://github.com/your-username/personal-mcp-context.git
cd personal-mcp-context
mkdir -p ~/context-data/personal2. Create initial index.json
cat > ~/context-data/personal/index.json << 'EOF'
{
"version": "2.0",
"nodes": [],
"links": [],
"metadata": {}
}
EOF3. Start the server
docker compose up -d --buildThe server will be available at http://127.0.0.1:3031 (localhost only).
4. Verify health
curl http://localhost:3031/healthClient Integration
OpenCode
Add to ~/.config/opencode/opencode.json:
"mcp": {
"personal-context": {
"type": "remote",
"url": "http://localhost:3031/mcp",
"enabled": true
}
}Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"personal-context": {
"command": "curl",
"args": ["-s", "http://localhost:3031/mcp"]
}
}
}Antigravity AGY
Add to ~/.gemini/antigravity/mcp_config.json:
{
"mcpServers": {
"personal-context": {
"serverUrl": "http://localhost:3031/mcp"
}
}
}Data Structure
Your context data lives in ~/context-data/ on your host machine (bind-mounted into the container). Files in this directory are not included in this repo and should never be committed (already in .gitignore).
~/context-data/
└── personal/
├── index.json # Knowledge graph (nodes + links)
├── personal.md # Your identity/profile
├── devices.md # Hardware info
├── servers.md # Server/infrastructure info
└── .backup/ # Auto-generated backupsLocal Development
npm install
npm run dev # Hot-reload via tsx
npm run build # Compile TypeScript
npm run test # Run Vitest testsSecurity Notes
⚠️ This server has NO authentication in its current MVP state. It is designed to run locally only (
127.0.0.1:3031). Do NOT expose this port to a public network without adding Bearer token auth first.
~/context-datais in.gitignore— never commit itPort is bound to
127.0.0.1only indocker-compose.ymlBefore deploying publicly (e.g., CapRover): add Bearer token auth + HTTPS
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/januarsyah901/personal-mcp-context'
If you have feedback or need assistance with the MCP directory API, please join our Discord server