Status: Future idea, not scheduled. Lives in the v0.5+ ""maybe"" bucket of the roadmap.
Summary
Wrap MCP (Model Context Protocol) servers as ToolT instances. Lets agents use any MCP-exposed tool without per-server adapter code.
Why this matters
MCP is becoming a dominant standard for exposing tools to LLM agents. Built-in support would make temporal-agent-rs interoperable with the broader MCP ecosystem.
Why not scheduled
May rise into v0.3 or v0.4 depending on community interest. Defer until there's a concrete use case driving the priority.
Open questions
- Sync vs. streaming MCP transports?
- Per-MCP-server connection lifecycle (workflow-scoped, worker-scoped)?
- Authentication patterns?
Status: Future idea, not scheduled. Lives in the v0.5+ ""maybe"" bucket of the roadmap.
Summary
Wrap MCP (Model Context Protocol) servers as
ToolTinstances. Lets agents use any MCP-exposed tool without per-server adapter code.Why this matters
MCP is becoming a dominant standard for exposing tools to LLM agents. Built-in support would make
temporal-agent-rsinteroperable with the broader MCP ecosystem.Why not scheduled
May rise into v0.3 or v0.4 depending on community interest. Defer until there's a concrete use case driving the priority.
Open questions