Introducing Aerostack: Workflows, MCPs, and Intelligent Bots on the Edge

The Problem It starts with configuration sprawl. I was building a project and kept switching between three code editors — VS Code, Cursor, Windsurf. Each one handles MCP servers differently. Each one has its own config file format, its own way of specifying credentials, its own quirks around which MCP features it supports. If I wanted to use the same MCP — say, a PostgreSQL query tool — I configured it in Cursor's mcp.json , then again in VS Code's settings, then again when I opened a different project. Every new project, every machine switch, same configuration from scratch. But configuration sprawl is just the surface problem. Underneath it, there are four deeper ones. MCPs are isolated islands. You install five MCPs — a database, Jira, Slack, GitHub, a monitoring tool. Each one works on its own. But there's no orchestration layer. You can't say "query the database for recent errors, then if severity is critical, create a Jira ticket, then post a summary to Slack." Each MCP is a stan