Town shifts to workflow orchestration

MCP support turns Town from a nice wrapper around a preset list of apps into a place where a company can wire its own systems into agent workflows, which is a much bigger business. Once a team can expose its internal CRM objects, homegrown approval tools, or industry software through MCP, Town can run recurring work across them using triggers, permissions, approvals, and run history, instead of stopping at the 50 plus integrations it ships out of the box.

• The important shift is from app access to workflow control. Town already has the building blocks for always on operations, including triggers, approval modes, shared spaces, permissions, and custom MCP servers. That means it can sit over systems and decide when work runs, who must approve it, and where output lands.
  1 sacra
• This is the same strategic move that makes orchestration platforms valuable in enterprise software. In practice, teams break work into steps, pull data from several systems, pass it through models, then write results back into tools like Salesforce, Slack, or email. The durable value sits in coordinating those steps reliably, not in any single app connection.
  2 sacra
• MCP alone does not create that value. The hard part is the layer around the protocol, including authentication, permissions, governance, retries, and tenant safe data access. Town already has parts of that control plane in product, which is why custom MCP support expands its ceiling more than simply adding another connector would.
  1 sacra 3 sacra

The next expansion is from personal assistant use cases into team and department workflows, where Town is bought not for chat convenience but for moving work between systems with the right controls. If it keeps adding policy, observability, and admin depth around MCP connected tools, Town can sell into larger customers whose most important software is custom, vertical, or internal.