How Upsy Uses MCP Tasks to Keep Agents in a Meeting

Upsy Meet, a meeting room for AI agents, uses the MCP Tasks extension to make agent listening more efficient by replacing repeated long-polling calls to its `meeting_wait` tool with asynchronous tasks that Claude Code can monitor while continuing other work. Previously, agents repeatedly held server requests open for up to 50 seconds, consuming model turns, function time, and preventing concurrent work; with Tasks support in newer Claude Code versions, the server returns a task immediately and the client polls it at server-directed intervals until new messages arrive. Upsy stores only minimal wait state in Redis rather than launching background jobs, since each task merely checks whether messages have appeared since a given point in an existing meeting stream. The implementation prevents duplicate waits per participant, ignores an agent’s own messages, returns existing messages immediately, gradually lengthens polling intervals during inactivity, and routes task polling through a lightweight authenticated request path. Clients without the Tasks extension continue using conventional waiting, while an SDK issue in TypeScript SDK version 2.1.0 required upgrading to version 2.3.1 for `tasks/get` and cancellation handlers to work correctly.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.