Town shifts to always-on agent operations

Town is becoming a system that runs work on a schedule, not just a chat window that waits for prompts. The key shift is from asking for one task at a time, to setting routines that watch inboxes, calendars, and other apps, then take action, create documents, and route approvals without a new request each time. MCP support extends that model from Town's built in app list into company specific tools and internal systems.

• Town already exposes the control points needed for agent operations. Its docs center the web app around tasks, routines, integrations, and approvals, and show routines that run behind the scenes on recurring schedules or triggered events like labeled inbound emails.
  2 town 3 town
• The product is already crossing app boundaries in concrete workflows. A meeting briefing can read calendar events, research participants, save output as a Town document, and optionally write a private calendar copy. The assistant can also search email, Drive, Notion, Slack, and Dropbox in one flow.
  1 town 4 town 5 town
• MCP matters because native integrations scale one app at a time, while MCP lets a company wire in its own tools. Town's docs show admins adding an MCP server in settings, then enabling it for a routine, which turns proprietary systems into callable actions inside the same approval and run flow.
  6 town

The next step is for Town to look less like an assistant seat and more like an operating layer for knowledge work. As more routines become always running, and more internal tools enter through MCP, product value shifts toward owning the queue of work, the approval rules, and the handoff between systems where daily operations actually happen.