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 |
Capabilities
Features and capabilities supported by this server
| 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_workflow | Query a running workflow for its current state |
| signal_workflow | Send a signal to a running workflow |
| cancel_workflow | Cancel a running workflow execution |
| get_workflow_result | 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_workflow | Forcefully terminate a workflow execution |
| get_workflow_history | Get the complete event history of a workflow execution. Specify 'limit' to control the number of events (default: 1000). |
| get_workflow_event | Get a single workflow history event with decoded payload fields when present |
| start_activity | Start a new standalone Temporal activity execution |
| execute_activity | Execute a standalone Temporal activity and wait for result |
| get_activity_result | Get the result of a standalone activity |
| describe_activity | Get detailed information about a standalone activity execution |
| list_activities | List standalone activity executions based on a query. Specify 'limit' to control results and 'skip' for pagination. |
| count_activities | Count standalone activity executions matching a query |
| cancel_activity | Cancel a running standalone activity execution |
| terminate_activity | Forcefully terminate a standalone activity execution |
| batch_signal | Send a signal to multiple workflows matching a query. Specify 'limit' to control batch size (default: 100). |
| batch_cancel | Cancel multiple workflows matching a query with concurrent processing for speed. Use 'concurrency' to control parallel operations (default: 50). |
| batch_terminate | Terminate multiple workflows matching a query. Specify 'limit' to control batch size (default: 100). |
| batch_cancel_activities | Cancel multiple standalone activities matching a query with concurrent processing for speed. Use 'concurrency' to control parallel operations (default: 50). |
| batch_terminate_activities | Terminate multiple standalone activities matching a query. Specify 'limit' to control batch size (default: 100). |
| create_schedule | Create a new schedule for periodic workflow execution |
| list_schedules | List all schedules. Specify 'limit' to control the number of results (default: 100). Use 'skip' to paginate through results. |
| pause_schedule | Pause a schedule |
| unpause_schedule | Resume a paused schedule |
| delete_schedule | Delete a schedule |
| trigger_schedule | Manually trigger a scheduled workflow immediately |
| describe_schedule | Get detailed configuration and runtime information about a schedule, including its spec, action, state, recent executions, and upcoming action times |
| continue_as_new | 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 | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GethosTheWalrus/temporal-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server