temporal-mcp
Related Servers
Alternatives to temporal-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server for interacting with Temporal Cloud workflows across multiple regions, providing tools to list, describe, terminate, and retrieve step results from workflows via natural language.71-
- AlicenseNot gradedqualityCmaintenanceAn MCP server for Hatchet, the durable orchestration engine, enabling LLMs to inspect workflow definitions, runs, logs, and more, with optional mutating tools for triggering, canceling, and managing workflows.217 PyPIMIT
- AlicenseAqualityAmaintenanceMCP server exposing AI agent observability tools: list, inspect, and deterministically replay recorded agent execution traces for debugging failures.1Apache 2.0
- AlicenseAqualityBmaintenanceAn MCP server that provides cost and reliability observability for LLM and agent workflows. It records model calls and allows querying and aggregating telemetry data through MCP tools.6MIT
- AlicenseAqualityDmaintenanceMCP server that gives AI agents access to your application's OpenTelemetry traces for querying, analysis, and debugging.513 npm2MIT

prefect-mcp-serverofficial
AlicenseAqualityBmaintenanceAn MCP server for interacting with Prefect resources, enabling AI assistants to monitor, manage, and debug workflows.1453MIT
TDQS
Scored across 3 tools
Each tool targets a distinct aspect of workflow inspection: list_workflows returns filtered overviews, describe_workflow provides detailed state for a specific execution, and get_workflow_history returns the event sequence. There is no meaningful overlap between the tools.
All tool names follow a consistent lowercase verb_noun pattern: list_workflows, describe_workflow, get_workflow_history. The naming style is uniform and predictable.
Three tools form a focused read-only workflow inspection surface for Temporal. Each tool earns its place, and the count is well-scoped for the apparent purpose.
The set covers core inspection operations well, but it lacks common workflow management operations such as start, signal, terminate, or query. For a read-only observability server this would be complete, but for a general temporal-mcp toolset it has notable gaps.