Temporal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEFAULT_REGION | No | Default region for Temporal Cloud (us, eu, au, in) | us |
| TEMPORAL_API_KEY | Yes | Your Temporal Cloud API key | |
| TEMPORAL_ACCOUNT_ID | Yes | Your Temporal Cloud account ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_workflow_step_resultsA | Get processed step results from a workflow execution including resultUri, step names, durations, and success status. This is a compact summary perfect for analyzing what happened in each step without the full raw history. Use this to get the resultUri for downloading detailed step logs. |
| get_workflow_execution_historyA | Get the complete RAW execution history of a Temporal workflow. Returns all events from the workflow history including activity executions, signals, timers, etc. WARNING: This can be very large. Use get_workflow_step_results instead for a compact summary with resultUri. |
| list_workflow_executionsB | List workflow executions with optional filtering using Temporal visibility query syntax. Can filter by workflow type, status, start time, etc. |
| describe_workflow_executionC | Get detailed information about a workflow execution including its current status, history length, start time, close time, and more. |
| fetch_workflow_historyB | Convenience method to fetch complete workflow history using the workflow handle. Similar to get_workflow_execution_history but may be easier to use when you only have the workflow ID. |
| terminate_workflow_executionA | Terminate a running workflow execution. This immediately stops the workflow and marks it as terminated. |
| list_closed_workflow_executionsA | List workflow executions that have closed (completed, failed, terminated, etc.) within a specific time range. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Several tools are clearly distinct, but there is notable overlap: fetch_workflow_history largely duplicates get_workflow_execution_history, and list_closed_workflow_executions is a specialized subset of list_workflow_executions. Descriptions help clarify the differences, but an agent could easily pick the wrong tool.
Tool names consistently follow a verb_noun pattern using snake_case: get, list, describe, fetch, terminate. The naming is predictable and readable, with only a minor stylistic variation between get and fetch.
With 7 tools, the server is well-scoped for workflow inspection and management. Each tool covers a meaningful operation without unnecessary bloat.
The tool set covers workflow observation well: listing, describing, raw history, and step summaries. However, it lacks common lifecycle operations such as starting, signaling, canceling, or querying workflows, and terminate is the only mutation available.