No user-submitted related servers found.
Scored across 31 tools
Each tool targets a distinct Temporal resource and action: workflow lifecycle, activity lifecycle, batch operations, and schedules are clearly separated. Overlaps like start_activity vs execute_activity and get_workflow_event vs get_workflow_history are differentiated by descriptions. No two tools appear to do the same thing.
Tool names consistently use snake_case with a predictable verb_noun pattern (e.g., start_workflow, get_workflow_result, batch_cancel, create_schedule). Minor exceptions like continue_as_new and batch_signal are still readable and match Temporal terminology. No mixed conventions.
31 tools is heavy for an MCP server, though Temporal is a complex platform. Some consolidation is possible, such as combining pause_schedule and unpause_schedule into an update operation, and the batch variants add surface area. The count is borderline over-scoped rather than clearly wrong.
Core workflow, activity, batch, and schedule lifecycles are well covered, including start, query, signal, cancel, terminate, list, and describe operations. Minor gaps exist, such as no update_schedule or schedule execution listing, but agents can work around these for most tasks.