Moment 01
A TypeScript MCP server that supports local/private and public app modes with health checks, auth, workflow tooling, and multi-service integrations.
Overview
Why this system had to exist
I designed this orchestrator to reduce the operational overhead of running multiple MCP-facing services with different runtime expectations. Some environments needed local STDIO or HTTP access, while others needed a public app surface with stricter security and configuration guarantees. The project had to centralize those concerns without creating separate codebases for each mode.
Moment 02
Built a reusable MCP gateway that bridges local automation, public app deployment, and integration-heavy workflows.
Moment 03
Unified local private STDIO and public HTTPS modes, ensuring zero-trust secure access to terminal tools.
Stage 1 of 5
Continue
Problem
What was breaking down
Integration-heavy automation stacks often drift into one-off scripts, inconsistent auth rules, and brittle startup assumptions. That makes local testing easy to break and public exposure risky. The challenge was to support multiple runtime modes, enforce safe deployment requirements, and still keep the server flexible enough to expose specialized tools and workflows.
Moment 01
Deployment Model
Separate ad hoc setups
Moment 02
Startup Safety
Late runtime failures
Moment 03
Operations
Scattered scripts
Stage 2 of 5
Constraint map
Solution
The breakthrough and implementation path
I implemented a TypeScript MCP server with mode-aware startup validation, integration modules, operational scripts, and health tooling. The system supports local/private usage for development and secure public deployments for app-facing access, while keeping workflows, integrations, and service diagnostics in one place. That gave me a more reliable foundation for automation-heavy internal products.
Moment 01
The critical design move was to treat deployment intent as a first-class runtime mode. Once the server explicitly knows whether it is operating privately or publicly, it can validate environment requirements early, enforce bearer auth defaults, and expose only the right surfaces for the chosen environment.
Moment 02
TypeScript MCP Core
Moment 03
Mode-aware Runtime Validation
Stage 3 of 5
Build system
Results
Before vs after, without the clutter
Outcome metrics stay visible while comparison details are compressed into large readable cards instead of long stacked panels.
Before
Deployment Model
Separate ad hoc setups
After
Optimized resolution
Single multi-mode orchestrator
Stage 4 of 5
Measured impact
Architecture
Layered architecture with one consistent layout
Explore the operating layers and the shipped feature set in the same wider content frame used across the full case study.
Active layer
TypeScript MCP Core
Dual operating modes for private MCP and public app deployments
Ship 01
Dual operating modes for private MCP and public app deployments
Ship 02
Health checks, tunnel status, and deployment diagnostics
Ship 03
Large integration surface for GHL, n8n, Notion, ClickUp, and more
Ship 04
Workflow-oriented scripts for operations, maintenance, and portfolio tasks
Stage 5 of 5
Architecture live