temporal-mcp-server
Provides an MCP server that connects to a Temporal server to expose Temporal workflow history via an MCP tool (workflow_history) and a documentation-like MCP resource (test://resource).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README lists connection/env configuration but does not document TLS requirements, authentication, authorization scopes, or secret handling practices. Workflow history can contain sensitive data; ensure MCP endpoint is protected and that Temporal access is least-privilege. Scores reflect missing documented security controls in the provided materials.
⚡ Reliability
Best When
You need an MCP-compatible way to fetch Temporal workflow history for debugging/analysis and you can control access to the MCP server and Temporal backend.
Avoid When
You cannot restrict access to potentially sensitive workflow history data, or you require robust documented error semantics, rate limiting, and pagination behavior.
Use Cases
- • Inspect and reason about Temporal workflow execution history from an AI agent
- • Debug workflow behavior by retrieving event history by workflow_id and run_id
- • Build agent-assisted observability/workflow forensics using MCP tool calls
Not For
- • Triggering or mutating workflow state (based on available docs, it is read-only history exposure)
- • Production-grade secure multi-tenant deployment without additional auth/network controls
- • Use where workflow history must be constrained by fine-grained authorization
Interface
Authentication
No authentication/authorization mechanism is described in the provided README. Access control should be assumed to be handled outside the service (e.g., network restrictions) unless implemented in code not shown here.
Pricing
No pricing information provided.
Agent Metadata
Known Gotchas
- ⚠ Tool interface is only lightly documented; argument validation, required fields beyond workflow_id/run_id, and response format are not specified in README.
- ⚠ No guidance on pagination/limits for large histories; agents may need to handle truncation or timeouts if the server returns limited history.
- ⚠ No documented retry/backoff behavior; agents should implement safe retries on transient failures only.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for temporal-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.