The biggest shift in the stack was moving from scripts to tools. A script helps once. A tool can be called again, composed with other tools, logged, documented, and exposed to an AI agent.
Where it is now
The VPS runs a collection of PM2 services including MCP gateway, MCP gateway proxy, WordPress, Printify, PayPal, VPS, web tools, videogen, social, hostinger, bamclone, and several application services. Locally, T-V2 also keeps gateway manifests and legacy-superagent definitions for filesystem, HTTP, SQL, shell, drive overview, videogen, and person-finder capabilities.
The barriers
The barrier was not adding one more tool. It was preventing the tool layer from becoming another mess. Tool names, credentials, paths, policies, and process status all need to be knowable.
How I did it
The stack grew around manifests, PM2 service names, deploy notes, and a habit of verifying live behavior rather than assuming a folder edit equals production. The result is a tool fabric: local machine, T-drive, VPS, websites, and AI agents can all meet in the same operational space.