temporal-mcp-server
Provides a Model Context Protocol (MCP) server exposing tools for managing Temporal workflow orchestration (start/query/control/history) and schedule management. Supports running against local or remote Temporal instances, with Docker or PyPI-based execution, and configurable connection/TLS/API key settings.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Supports TLS-related configuration (including mTLS client cert/key) and an API key for connecting to Temporal. README does not detail how secrets are logged/handled internally, nor does it describe authorization scopes/RBAC for MCP tools. Network exposure controls (e.g., bind address/firewall) and MCP-side auth are not documented here.
⚡ Reliability
Best When
When you want a standardized MCP interface to Temporal that can be consumed by MCP clients (e.g., IDEs/agents) to orchestrate workflows and schedules programmatically.
Avoid When
When you require a fully documented REST/SDK experience, OAuth-style delegated authorization, or guaranteed idempotency/retry semantics for every operation.
Use Cases
- • Letting AI agents start Temporal workflows and await results
- • Enabling agent-driven workflow inspection (describe, query, history)
- • Agent-driven operational control (signal, cancel, terminate, continue-as-new)
- • Batch operations for signals/cancels/terminations over workflow queries
- • Managing Temporal schedules (create/list/pause/unpause/delete/trigger)
Not For
- • High-assurance production deployments without verifying operational safety and error handling semantics
- • Use as a public internet-facing service without proper network controls and transport security validation
- • Workloads requiring complex, fine-grained authorization beyond a single API key
Interface
Authentication
Authentication is described as a Temporal API key and/or mTLS configuration for the Temporal connection. The README does not describe MCP-side user auth, authorization scopes, or RBAC at the tool level.
Pricing
No pricing information provided (open-source package implied by Apache-2.0, but no explicit statement). Costs would primarily be from running Temporal and operating MCP clients.
Agent Metadata
Known Gotchas
- ⚠ Operations like start_workflow/control actions are likely not inherently idempotent; agents may need to avoid duplicate starts and handle retries carefully.
- ⚠ Batch operations rely on query filters; agents should ensure queries are precise to avoid unintended workflow selection.
- ⚠ Pagination is indicated via limit/skip for list endpoints; agents should loop until completion to avoid truncated results.
- ⚠ Tool semantics (e.g., behavior of cancel/terminate/continue-as-new, and how results are represented) are not described in README, so agents may need to validate against Temporal behavior.
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.