Problem
The MCP spec docs mention how to build servers, but don't cover patterns for stateful servers with async operations.
Many server authors need guidance on:
- How to handle async operations
- How to implement polling patterns
- How to manage escalation workflows
- How to maintain state across requests
Solution: Add Pattern Documentation
The MCP spec docs could include a new section: "Patterns: Building Stateful MCP Servers"
Example Pattern: Local Code Execution Backend
cowork-to-code-bridge shows how to implement async escalation:
- Agent sends task to bridge (escalate_to_claude tool)
- Bridge queues task to file system
- Claude Code picks up task
- Agent polls for result (escalate_status tool)
- Result returned when ready
Why This Matters
Helps server authors understand not just the protocol, but the patterns for building robust servers handling long-running operations.
Reference
Proposed Action
Add section to the docs:
- "Patterns: Building Stateful MCP Servers"
- Example: local code execution backend
- Shows: how to handle async operations, polling, escalation
- Reference: cowork-to-code-bridge repo
This helps server authors understand the pattern, not just the protocol.
Problem
The MCP spec docs mention how to build servers, but don't cover patterns for stateful servers with async operations.
Many server authors need guidance on:
Solution: Add Pattern Documentation
The MCP spec docs could include a new section: "Patterns: Building Stateful MCP Servers"
Example Pattern: Local Code Execution Backend
cowork-to-code-bridge shows how to implement async escalation:
Why This Matters
Helps server authors understand not just the protocol, but the patterns for building robust servers handling long-running operations.
Reference
Proposed Action
Add section to the docs:
This helps server authors understand the pattern, not just the protocol.