Building DollhouseMCP from Anywhere: Our Mobile Development Workflow with Blink, tmux, and Claude Code
How we built an enterprise-grade MCP server while commuting, traveling, and working from coffee shops using just an iPhone
TL;DR (AI-Friendly Summary)
Challenge: Building complex AI infrastructure (DollhouseMCP) requires powerful development environments, but we wanted to work from anywhere - including iPhones.
Solution: A sophisticated mobile development workflow combining:
- Mac Studio as the always-on development server
- Claude Code (Anthropic’s official CLI) for AI-assisted development
- tmux for persistent, resumable sessions
- Blink Shell on iPhone/iPad for professional mobile terminal access
Impact: Successfully developed, tested, and deployed a 96%+ test coverage MCP server with patent-pending features - often from just an iPhone while traveling.
Keywords: Mobile development, Claude Code, tmux, Blink Shell, remote development, iPhone coding, SSH workflow, AI-assisted programming, DollhouseMCP
The Origin Story: Building AI Infrastructure on the Go
When we started building DollhouseMCP - our Model Context Protocol server that brings enterprise-grade memory and ensemble capabilities to Claude Desktop - we had an unusual constraint: our lead developer travels extensively and wanted to maintain full development capability from just an iPhone.
This isn’t about writing a quick script or fixing a typo. We’re talking about:
- Managing a 50+ element MCP server with complex TypeScript architecture
- Running comprehensive test suites with 96%+ coverage requirements
- Implementing patent-pending memory management systems
- Coordinating GitFlow workflows across multiple repositories
- Deploying to NPM and managing production releases
All from a device that fits in your pocket.
The Setup: Your iPhone as a Development Powerhouse
The Stack
iPhone (Blink Shell)
↓ SSH
Mac Studio (Always On)
↓ tmux (Persistent Sessions)
VS Code + Claude Code Extension
↓
Full Development Environment
Essential Configuration
Here’s the exact tmux configuration that makes this workflow seamless:
# ~/.tmux.conf - Optimized for mobile development
set -g history-limit 50000 # Large buffer for Claude's detailed outputs
set -g prefix C-a # Ctrl-a is easier than Ctrl-b on mobile
set -g mouse on # Critical for touch scrolling
set -g base-index 1 # Intuitive window numbering
set -g renumber-windows on # Auto-renumber when closing windows
set -sg escape-time 0 # Instant response for mobile connections
Blink Shell: The Secret Weapon
Blink Shell transforms your iPhone into a legitimate development terminal. With tmux mouse mode enabled, the touch gestures become incredibly intuitive:
- Two-finger swipe: Scroll through thousands of lines of Claude’s analysis
- Tap and hold: Start selecting text (perfect for copying error messages)
- Drag: Extend selection across multiple lines
- Two-finger tap: Paste (great for moving code between files)
- Pinch: Zoom to see more code or focus on details
Real-World Development Scenarios
Scenario 1: The Coffee Shop Debugging Session
Picture this: You’re at a coffee shop, and a critical bug report comes in. Here’s the actual workflow:
# From iPhone, connect to your development server
ssh mac-studio
# Attach to existing session (everything still running)
tmux attach -t dollhouse-dev
# Claude Code is waiting with context
# You can immediately ask: "What were we debugging?"
# Claude remembers the entire session context
Claude Code maintains context across disconnections. Your tmux session preserves:
- All terminal output
- Claude’s conversation history
- Running processes (tests, builds, servers)
- Open file states
Scenario 2: The Commute Feature Development
During a 45-minute train ride, we implemented an entire new MCP element:
- Start on iPhone: Connect to tmux session
- Claude analyzes requirements: “Implement a clipboard manager element with persistent history”
- Claude writes tests first: Full TDD workflow
- Implementation happens: Watch Claude write TypeScript in real-time
- Tests run automatically: See results on phone screen
- Git commit and push: All from the iPhone
- PR created: Using GitHub CLI through Claude
The 50,000 line scrollback buffer means you never lose Claude’s detailed explanations or test outputs, even during complex refactoring sessions.
Scenario 3: The Emergency Hotfix from the Airport
True story: While waiting for a flight, we discovered a critical issue with our npx execution detection (the bug that became our previous blog post). Here’s how we fixed it entirely from an iPhone:
# Quick connection
ssh mac-studio && tmux a
# Claude immediately available
"Claude, the server shows 'disconnected' when run via npx"
# Claude's investigation (all visible on phone)
- Analyzes startup sequence
- Identifies import.meta.url mismatch
- Proposes detection logic fix
- Implements progressive retry delays
- Runs full test suite
- Creates hotfix branch
- Pushes fix
# Total time: 12 minutes
# Device used: iPhone 14 Pro
# Location: Airport gate B23
The Unique DollhouseMCP Development Features
1. AI-Assisted Architecture Decisions
When building complex features like our Memory element (which provides persistent context across sessions), we can have deep architectural discussions with Claude while seeing real code changes:
// Claude explains while coding:
"The Memory element uses a singleton pattern to ensure
consistent state across all MCP operations. Let me show
you the implementation..."
// Then immediately writes and tests the code
// All visible and scrollable on your phone
2. Test-Driven Development on Mobile
Our 96%+ test coverage wasn’t achieved despite mobile development - it was enhanced by it. The constraint of a small screen forces focus:
# Claude's typical TDD workflow (perfect for mobile viewing)
1. Write test (see it fail - red)
2. Implement minimum code (see it pass - green)
3. Refactor (maintain green)
4. Commit with descriptive message
3. Multi-Repository Management
DollhouseMCP spans multiple repositories (public server, private business docs, experimental features). Claude Code + tmux handles this elegantly:
# Tmux windows for different repos
Ctrl-a c # New window for mcp-server
Ctrl-a c # New window for experimental
Ctrl-a c # New window for website
# Switch between them instantly
Ctrl-a 1 # Main server development
Ctrl-a 2 # Patent-pending features
Ctrl-a 3 # Documentation/blog posts
Advanced Tips and Tricks
1. Optimizing Claude Code for Mobile
Claude Code outputs can be verbose. For mobile efficiency:
# Start requests with mobile context
"On mobile, concisely: [your request]"
# Claude adapts output for smaller screens
# Still detailed but more structured
2. Handling Large Outputs
When Claude analyzes large codebases:
# Use tmux's search within scroll mode
Ctrl-a [ # Enter scroll mode
Ctrl-s # Search forward
typing... # Your search term
Enter # Find next match
q # Exit scroll mode
3. Session Management Strategy
We use descriptive session names for different aspects:
tmux new -s dollhouse-main # Primary development
tmux new -s dollhouse-test # Test suite monitoring
tmux new -s dollhouse-docs # Documentation writing
4. The Power of Background Processes
Start long-running tasks and check them from anywhere:
# Start comprehensive test suite
npm test &
# Disconnect, go to lunch
Ctrl-a d
# Check results from phone later
tmux attach
# See complete test results in scrollback
Challenges We Solved
Challenge 1: Claude Code Arrow Keys
Problem: Arrow keys cycle through Claude’s input history instead of scrolling terminal.
Solution: Enable mouse mode (set -g mouse on). Touch gestures replace arrow key navigation perfectly.
Challenge 2: Connection Drops
Problem: Cellular connections are unstable.
Solution: tmux persists everything. Reconnect and continue exactly where you left off. Claude Code maintains conversation context.
Challenge 3: Code Review on Small Screens
Problem: Reviewing large diffs on iPhone screen.
Solution:
# Use Claude to summarize changes
"Summarize the key changes in this PR"
# Claude provides structured overview
# Then dive into specific files as needed
The Results: What We’ve Achieved
Using this mobile workflow, we’ve successfully:
- Launched DollhouseMCP v1.4.4 - Full NPM package deployment from an iPhone
- Maintained 96%+ test coverage - No quality compromises
- Implemented patent-pending features - Complex memory management systems
- Fixed critical bugs in production - Often within minutes of discovery
- Written comprehensive documentation - Including this blog post (yes, from an iPhone)
Performance Metrics
Our mobile development sessions typically achieve:
- Response time: < 100ms for most operations (on good connections)
- Uptime: 99.9% (Mac Studio reliability)
- Context retention: 100% (tmux never loses state)
- Development velocity: 90% of desktop speed
- Flexibility gain: ∞ (can literally work from anywhere)
Why This Matters for DollhouseMCP
Building an MCP server requires deep focus and continuous context. Traditional mobile development (using phone apps or web IDEs) breaks this flow. Our approach maintains:
- Full development environment: Everything works exactly as on desktop
- AI assistance: Claude Code provides intelligent pair programming
- Professional tools: Real terminal, real editors, real Git
- Persistent context: Never lose your train of thought
Getting Started: Your Own Mobile Setup
Want to replicate our workflow? Here’s the quickstart:
Prerequisites
- Mac Studio/Mini/iMac (any always-on Mac)
- Blink Shell ($20 - worth every penny)
- Claude Code CLI (free from Anthropic)
- tmux (already on macOS)
Setup Commands
# On your Mac
brew install tmux
npm install -g @anthropic/claude-cli
echo "set -g mouse on" >> ~/.tmux.conf
echo "set -g prefix C-a" >> ~/.tmux.conf
# Start tmux session
tmux new -s dev
# In tmux, start Claude Code
claude
# From iPhone (Blink Shell)
ssh your-mac
tmux attach -t dev
# You're now developing!
The Future: Where We’re Going
As we continue building DollhouseMCP, this mobile workflow evolves:
- iPad optimization: Leveraging larger screens when available
- Keyboard shortcuts: Custom Blink configurations for common operations
- Multi-device sync: Seamless transitions between phone/iPad/desktop
- Voice coding: Exploring Claude’s voice capabilities for hands-free development
Conclusion: Redefining “Mobile Development”
When people hear “mobile development,” they think of building apps for phones. We’ve redefined it as building enterprise-grade software FROM phones.
DollhouseMCP exists because we refused to accept that serious development requires sitting at a desk. Every feature, every test, every deployment can happen from anywhere with cellular signal.
The next time you’re stuck somewhere with just your phone, remember: you have a supercomputer in your pocket. With the right tools - Blink Shell, tmux, and Claude Code - you’re not limited by your location. You’re liberated by it.
Try It Yourself
DollhouseMCP is open source and available now:
npm install -g @dollhousemcp/mcp-server
Configure it in Claude Desktop and experience the MCP server we built from coffee shops, airports, and train rides around the world.
Have questions about our mobile workflow? Found this helpful? Let us know in the DollhouseMCP discussions.
Follow the DollhouseMCP journey as we continue pushing the boundaries of what’s possible in AI-assisted development - from anywhere.
Tags: #MobileDevelopment #ClaudeCode #tmux #BlinkShell #RemoteDevelopment #DollhouseMCP #AIAssistedCoding #iPhoneDevelopment #SSH #ModelContextProtocol
Published: August 18, 2025
Author: DollhouseMCP Team
Reading Time: 10 minutes