Temporal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEMPORAL_HOST | No | Temporal server host and port | localhost:7233 |
| TEMPORAL_API_KEY | No | API key for authentication (enables TLS automatically) | |
| TEMPORAL_NAMESPACE | No | Temporal namespace | default |
| TEMPORAL_TLS_ENABLED | No | Enable TLS (auto-detected if API key or mTLS cert/key provided) | false |
| TEMPORAL_TLS_CLIENT_KEY_PATH | No | Path to mTLS client key | |
| TEMPORAL_TLS_CLIENT_CERT_PATH | No | Path to mTLS client certificate |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_workflowC | Start a new Temporal workflow execution |
| query_workflowB | Query a running workflow for its current state |
| signal_workflowB | Send a signal to a running workflow |
| cancel_workflowC | Cancel a running workflow execution |
| get_workflow_resultA | Get the result of a completed workflow |
| describe_workflowC | Get detailed information about a workflow execution |
| list_workflowsA | List workflow executions based on a query. Specify 'limit' to control the number of results (default: 100, max recommended: 1000). Use 'skip' to paginate through results. |
| terminate_workflowC | Forcefully terminate a workflow execution |
| get_workflow_historyB | Get the complete event history of a workflow execution. Specify 'limit' to control the number of events (default: 1000). |
| get_workflow_eventB | Get a single workflow history event with decoded payload fields when present |
| start_activityB | Start a new standalone Temporal activity execution |
| execute_activityA | Execute a standalone Temporal activity and wait for result |
| get_activity_resultC | Get the result of a standalone activity |
| describe_activityB | Get detailed information about a standalone activity execution |
| list_activitiesB | List standalone activity executions based on a query. Specify 'limit' to control results and 'skip' for pagination. |
| count_activitiesB | Count standalone activity executions matching a query |
| cancel_activityB | Cancel a running standalone activity execution |
| terminate_activityC | Forcefully terminate a standalone activity execution |
| batch_signalB | Send a signal to multiple workflows matching a query. Specify 'limit' to control batch size (default: 100). |
| batch_cancelB | Cancel multiple workflows matching a query with concurrent processing for speed. Use 'concurrency' to control parallel operations (default: 50). |
| batch_terminateB | Terminate multiple workflows matching a query. Specify 'limit' to control batch size (default: 100). |
| batch_cancel_activitiesC | Cancel multiple standalone activities matching a query with concurrent processing for speed. Use 'concurrency' to control parallel operations (default: 50). |
| batch_terminate_activitiesC | Terminate multiple standalone activities matching a query. Specify 'limit' to control batch size (default: 100). |
| create_scheduleB | Create a new schedule for periodic workflow execution |
| list_schedulesB | List all schedules. Specify 'limit' to control the number of results (default: 100). Use 'skip' to paginate through results. |
| pause_scheduleC | Pause a schedule |
| unpause_scheduleB | Resume a paused schedule |
| delete_scheduleC | Delete a schedule |
| trigger_scheduleA | Manually trigger a scheduled workflow immediately |
| describe_scheduleA | Get detailed configuration and runtime information about a schedule, including its spec, action, state, recent executions, and upcoming action times |
| continue_as_newC | Signal a workflow to continue as new (restart with new inputs while preserving history link) |
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 31 tools
Tools are clearly organized by resource (workflows, activities, schedules, batches) and mostly target distinct actions, so an agent can usually pick correctly. However, start_activity vs execute_activity overlap heavily, and cancel vs terminate pairs require close reading to distinguish.
All tools use snake_case and follow a consistent verb + resource + detail pattern, such as list_workflows, describe_activity, and pause_schedule. The batch_* prefix is also applied uniformly, and continue_as_new is a minor but acceptable stylistic outlier.
31 tools is well above the 25-tool threshold and feels heavy for an agent to reliably navigate, even though workflows, activities, and schedules justify some breadth. The set would benefit from consolidation or clearer scoping into separate servers.
The tool set covers workflow, activity, and schedule lifecycles thoroughly, including result retrieval, history, signals, querying, and batch operations. Minor gaps exist—such as workflow update/reset and schedule update—but they are not critical for common Temporal operations.