MCP Infrastructure System
MCP Infrastructure System
The Problem
AI assistants operate with limited context. They can’t see your filesystem, access your git history, or interact with external services without manual intervention.
Every new conversation starts from scratch unless you copy-paste context repeatedly. Inefficient.
The Solution
Model Context Protocol (MCP) provides modular capabilities through specialized servers. Think of them as sense organs for AI—each server grants access to a different type of information or action.
Architecture
6 MCP Servers Running:
- Filesystem MCP - Read/write files, search directories, manage file metadata
- Git MCP - Repository status, diffs, commits, branch management
- GitHub MCP - Remote repo access, PRs, issues, commit history
- Memory MCP - Knowledge graph for entity tracking and relationships
- Fetch MCP - Web content retrieval and processing
- Shared Context MCP - Cross-machine state synchronization
Configuration Strategy
Two-tier approach:
- Template (synced via git) - Reference configuration in
gf-labs/.mcp.json - Active (local, machine-specific) - Actual config in
~/.mcp.json
Each machine adapts the template to its own paths and environment.
What Makes It Interesting
Modularity: Each server provides distinct capabilities. You can mix and match based on needs.
Stateful AI: The Memory MCP turns ephemeral conversations into persistent knowledge graphs.
Cross-Machine Continuity: Shared Context MCP syncs state between my Mac and Z13 in real-time via Upstash Redis.
OAuth-Based: GitHub MCP uses OAuth instead of personal access tokens—cleaner security model.
Current Status
All 6 servers operational and tested. GitHub MCP successfully queries repositories. Shared Context MCP syncs between machines. Git MCP handles local repository operations.
The infrastructure is stable. Now I’m exploring what becomes possible when AI has this level of environmental awareness.
Technologies: Model Context Protocol, Node.js, Python, Upstash Redis, GitHub OAuth Status: Operational Source: Private infrastructure setup