Temporal
Cloud-native workflow orchestration platform for building reliable distributed applications
Verdict
Common use cases
- Cancel stalled workflows during incident response
- Signal running workflows to update config
- Query workflow states across environments
- Batch-reset workflows stuck in bad state
- Audit workflow execution counts by task queue
Integration
- Vendor
- Temporal
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 49
- Composio slug
temporal
Tools
- Batch Cancel Workflows
Request cancellation of selected Temporal Workflows. Cancellation is cooperative: Workflow code can perform cleanup and external side effects before closing. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for th
- Batch Delete Workflowsdestructive
WARNING: Permanently delete selected Temporal Workflow Executions and their Event Histories. This cannot be undone. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for the observed scope; its approximate count is
- Batch Reset Workflows
WARNING: Irreversibly reset selected Temporal Workflows. Each successful reset terminates the current run and creates a new run; replay and reapplied events can repeat application code and external side effects. Preview the exact Visibility
- Batch Signal Workflows
Send a named Signal to selected Temporal Workflows. Signal handlers run application code and can cause arbitrary, non-idempotent external side effects. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for the obse
- Batch Terminate Workflows
WARNING: Irreversibly terminate selected Temporal Workflows immediately; Workflow cleanup code does not run. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain approval for the observed scope; its approximate count is not a
- Batch Update Workflow Options
Update typed execution options on selected Temporal Workflows. Worker routing, task priority, and virtual-time changes can cause application and external side effects. Preview the exact Visibility query with COUNT_WORKFLOWS and obtain appro
- Cancel Workflow
Irreversibly request cooperative cancellation of a running Temporal Workflow Execution. Temporal records a cancellation-requested event and schedules a Workflow Task, but the Workflow may delay or ignore cancellation depending on its code.
- Count Workflows
Return an approximate count of Workflow Executions matching a Temporal Visibility query, including supported grouped counts. Requires Namespace Read access.
- Create Export Sink
Create a persistent Temporal Cloud Workflow History export sink asynchronously. Requires Namespace Admin access. Warning: an enabled sink writes closed Workflow Histories to external storage on an ongoing schedule and may incur storage cost
- Delete Export Sinkdestructive
Delete a Temporal Cloud Workflow History export sink asynchronously. Requires Namespace Admin access. WARNING: this irreversibly stops future exports from the sink. Files already exported to external storage remain there and must be managed
- Delete Namespacedestructive
Permanently and irreversibly delete a Temporal Cloud Namespace and all of its Workflow data asynchronously. WARNING: there is no recovery or undo. Use only for a verified disposable Namespace after confirming its full ID, contents, latest r
- Describe Batch Operation
Return progress, state, selection query, type, and failure counts for one batch operation in an authorized Temporal Cloud Namespace. Requires Namespace Read access.
- Describe Namespace
Return one Temporal Cloud Namespace's configuration, resource version, routing endpoints, state, limits, and capacity. Requires Namespace Read access.
- Describe Workflow
Return configuration, status, pending work, callbacks, and child state for one Workflow Execution in an authorized Temporal Cloud Namespace. Omit run_id to describe the current run. Requires Namespace Read access.
- Fail Over Namespace Region
Switch a multi-region Temporal Cloud Namespace's active region asynchronously. WARNING: This operation disrupts current Namespace routing while failover completes. Require explicit approval and a documented rollback or failback plan before
- Get Async Operation
Return the current state and failure details of a Temporal Cloud asynchronous operation.
- Get Export Sink
Return one Temporal Cloud Workflow History export sink, including its resource version, destination configuration, state, and health. Requires Namespace Read access.
- Get Namespace Capacity
Return a Temporal Cloud Namespace's capacity mode, available limits, and seven-day actions-per-second statistics. Requires Namespace Read access.
- Get Workflow History
Return one page of a Temporal Workflow Execution's Event History in forward or reverse order. Requires Namespace Read access.
- List Archived Workflows
Return one page of archived Workflow Executions matching an exact Temporal Visibility query. Requires Namespace Read access and a Namespace deployment with archival visibility configured and available; the probed Namespace returned HTTP 403
- List Batch Operations
Return one page of batch operations in an authorized Temporal Cloud Namespace. Requires Namespace Read access.
- List Cloud Regions
List currently available Temporal Cloud regions for Namespace placement.
- List Export Sinks
Return one page of Workflow History export sinks configured on a Temporal Cloud Namespace. Requires Namespace Read access.
- List Namespace Assignments
Return one page of users, User Groups, or Service Accounts assigned to a Temporal Cloud Namespace. Requires Namespace Read access.
- List Namespaces
Return one page of Temporal Cloud Namespaces visible to the API-key identity, optionally filtered by name or Project.
- List Workflows
Search one page of Workflow Executions in an authorized Temporal Cloud Namespace using Temporal Visibility query syntax. Requires Namespace Read access.
- Move Namespace To Project
Move a Temporal Cloud Namespace to another Project asynchronously. WARNING: this disruptive operation can change inherited access and connectivity. Verify the source and destination Projects, preserve required connectivity rules, and obtain
- Pause Workflow
Pause one Temporal Workflow Execution. Temporal changes its status to PAUSED, records a WORKFLOW_EXECUTION_PAUSED event, stops dispatching new Workflow and Activity Tasks, pauses executing Activities, and rejects Queries and Updates; an exe
- Query Workflow
Run a synchronous, read-only Query handler against one Temporal Workflow Execution. The handler runs in Workflow context but cannot mutate Workflow state. Requires Namespace Read access.
- Register Namespace
Create a billable, persistent Temporal Cloud Namespace asynchronously and return its full Namespace ID and operation ID. The name and replicas are immutable, and custom Search Attributes cannot be deleted. Use a unique disposable name for t
- Remove Namespace Accessdestructive
Remove one user's, user group's, or service account's direct permission on a Temporal Cloud Namespace by setting PERMISSION_UNSPECIFIED. Requires Namespace Admin. WARNING: this can immediately remove access or lock out the selected identity
- Rename Custom Search Attribute
Rename one custom Search Attribute in a Temporal Cloud Namespace asynchronously. This is a potentially breaking schema mutation: Temporal does not rewrite application Visibility queries or dashboards that reference the old name. Verify all
- Replace Workflow
Replace a running Workflow Execution with a new execution using the same Workflow ID. WARNING: if that ID is running, Temporal irreversibly terminates the existing execution before starting the replacement. This may interrupt in-flight work
- Reset Workflow
WARNING: Irreversibly reset a Temporal Workflow to a selected Workflow Task event. Temporal terminates the current run and creates a new run; replay and reapplied events can repeat application code and external side effects. Verify the sour
- Set Namespace Access
Set one user's, user group's, or service account's direct ADMIN, WRITE, or READ permission on a Temporal Cloud Namespace. The new permission replaces that principal's current direct access; setting a lower permission may lock out the caller
- Signal With Start Workflow
Atomically signal a running Temporal Workflow or start and signal it when absent. This may run application code and trigger external side effects; use a stable request_id when retrying the same intent. The TERMINATE_EXISTING conflict policy
- Signal Workflow
Send an asynchronous Signal to one running Temporal Workflow Execution. This records a history event, schedules Workflow code, and may trigger arbitrary external business side effects. Temporal's successful response only confirms acceptance
- Start or Get Workflow
Start a Workflow Execution, or return the already-running execution when the Workflow ID conflicts. This action never replaces the running execution. The response has started=false when it returns the existing execution. Starting a Workflow
- Start Workflow
Start a new Workflow Execution in an authorized Temporal Cloud Namespace. The request fails if the Workflow ID is already running; use Start or Get Workflow or Replace Workflow only when those different conflict semantics are intended. This
- Stop Batch Operation
Request that Temporal stop an in-progress batch operation. This does not roll back Workflows already processed by the batch: their cancellations, terminations, signals, deletions, resets, or option changes remain in effect. Requires Namespa
- Terminate Workflow
Immediately and irreversibly terminate one Temporal Workflow Execution. WARNING: termination bypasses cooperative cancellation and Workflow cleanup logic, so finally blocks, compensation, and pending work may not run. Use cancellation inste
- Trigger Workflow Rule
Trigger an existing configured Temporal Workflow Rule against one Workflow Execution. This irreversible request evaluates the rule and, when its conditions match, may run configured actions with destructive or arbitrary external side effect
- Unpause Workflow
Resume a paused Temporal Workflow Execution. Unpausing changes its status to running, records an unpaused history event, and resumes application code in Workflow and Activity Tasks, which may produce external side effects. Use request_id fo
- Update Export Sink
Update an existing Temporal Cloud Workflow History export sink asynchronously using optimistic concurrency. WARNING: this replaces the sink's destination configuration or enabled state for future exports and may redirect or stop Workflow Hi
- Update Namespace
Update a Temporal Cloud Namespace specification asynchronously using the latest resource version for optimistic concurrency. WARNING: this full-spec replacement can change retention, regions, capacity, authentication, deletion protection, a
- Update Namespace Tags
Upsert or permanently remove tags on a Temporal Cloud Namespace asynchronously; removed tags no longer exist on the Namespace. At least one of tags_to_upsert or tags_to_remove must be non-empty, and the same key cannot appear in both. The A
- Update Workflow
Send a durable Update to one Temporal Workflow Execution and wait for the requested lifecycle stage. The Workflow handler may mutate state and cause arbitrary external business side effects. Reuse update_id only when retrying the same inten
- Update Workflow Options
Update selected options on one Temporal Workflow Execution using an exact protobuf FieldMask. This mutation can reroute Workflow Tasks to different Workers, change task priority, or alter virtual-time behavior and thereby cause application
- Validate Export Sink
Validate a Temporal Cloud Workflow History export sink configuration. WARNING: this is not read-only; Temporal writes an empty test object to the configured external bucket or container. Use only an owner-approved disposable bucket or conta
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration', search for Temporal, and select it from the developer tools category. 3. You'll be prompted to enter a Temporal API key — generate one in your Temporal Cloud account under Settings > API Keys with at least Namespace Read and Workflow Write scopes. 4. Paste the key into Switchy and choose which Temporal namespace you want this integration to access (you can connect multiple namespaces by adding separate integrations). 5. Click 'Connect' and wait for the green confirmation banner. 6. Open any Project, type '@Temporal count workflows where TaskQueue="critical-jobs"' in the chat, and send — if you see a count response, the connection works. 7. To invoke batch operations, always preview with count_workflows first, then reference the query in your batch command so the MCP can confirm scope.
What teammates see: by default, memories from Temporal are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Count Stuck Workflows
@Temporal count workflows where TaskQueue="data-pipeline" and ExecutionDuration > 3600s
Cancel Long-Running Jobs
@Temporal batch cancel workflows where WorkflowType="ProcessUpload" and StartTime < 2024-01-01. Preview the count first, then confirm.
Signal Active Workflows
@Temporal batch signal workflows where TaskQueue="user-onboarding" with signal name "update_feature_flags" and payload {"new_flags": ["dark_mode"]}Reset Failed Workflows
@Temporal batch reset workflows where WorkflowType="PaymentProcessor" and ExecutionStatus="Failed" to last successful event. Preview count and confirm scope.
Audit Workflow Distribution
@Temporal count workflows grouped by TaskQueue for the last 24 hours
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@temporal show me all workflows in the 'production' namespace that have been running longer than 24 hours and are still open
Found 47 open Workflow Executions in namespace 'production' running >24h: • order-fulfillment-wf (ID: ord_89x2k) – Running 38h, WorkflowType: OrderFulfillmentWorkflow, Status: Running • payment-retry-wf (ID: pay_7m3n) – Running 29h, WorkflowType: PaymentRetryWorkflow, Status: Running • data-migration-wf (ID: mig_4k8p) – Running 26h, WorkflowType: DataMigrationWorkflow, Status: Running [...44 more] This illustrative example shows how Temporal's Visibility query surfaces long-running executions. Actual results depend on your Workflow history and indexing configuration.
Demonstrates read-heavy Visibility queries across Temporal's durable execution state. Requires Namespace Read permission. Query performance depends on your cluster's Elasticsearch/database indexing; large result sets may paginate or timeout. Useful for operational monitoring but not real-time alerting.
@temporal send a 'priority_escalation' signal to all workflows in the 'orders' namespace with WorkflowType 'OrderProcessingWorkflow' that are currently waiting
Batch Signal preview for namespace 'orders': Visibility query: WorkflowType='OrderProcessingWorkflow' AND ExecutionStatus='Running' Estimated match count: ~23 Workflow Executions Signal name: priority_escalation Payload: (empty) WARNING: Signal handlers execute application code. If your OrderProcessingWorkflow's priority_escalation handler triggers external API calls (inventory reservation, shipping acceleration), those side effects will occur 23 times and are NOT idempotent. Confirm you want to proceed with batch signaling.
Showcases Temporal's cooperative communication model—Signals invoke Workflow code that can trigger real-world side effects (API calls, database writes). Always preview the COUNT before batch operations. Non-idempotent handlers mean duplicate signals can cause duplicate external actions. Requires Namespace Write and Signal permissions.
@temporal analyze the last 50 failed workflows in 'payments' namespace and draft a summary of the top 3 failure reasons with recommended fixes
Analyzed 50 failed Workflow Executions in namespace 'payments' (last 7 days): **Top Failure Reasons:** 1. **ActivityTaskTimedOut (28 occurrences, 56%)** – Activities 'charge_card' and 'verify_funds' exceeded 30s timeout. Recommendation: Increase Activity timeout to 60s or implement exponential backoff retry policy in Worker configuration. 2. **ApplicationFailure: 'InsufficientFunds' (14 occurrences, 28%)** – Payment gateway returned non-retryable error. Recommendation: Add explicit error handling in Workflow to transition to 'pending_manual_review' state instead of failing. 3. **WorkerShutdown (8 occurrences, 16%)** – Worker process terminated mid-execution. Recommendation: Enable graceful shutdown hooks and verify Worker deployment stability. This illustrative synthesis combines Temporal's Event History data with AI reasoning to surface actionable patterns.
Pairs Temporal's durable execution logs with AI analysis to identify operational patterns humans might miss. The MCP provides raw failure data; the AI synthesizes trends. Requires Read access to Event Histories. Most valuable when you have enough failure volume to spot patterns—less useful for one-off errors.
Use-case deep-dives
When batch operations beat manual workflow wrangling during outages
A 6-person platform team runs 200+ incident-response workflows during a database failover. Half are stuck waiting on a dead service; the other half need re-routing to a backup region. Temporal's batch signal and batch update tools let the on-call engineer fix all stuck workflows in two operations instead of 200 manual clicks. The preview-then-execute pattern (count workflows, verify the query, then batch signal) prevents accidental signals to production workflows. This MCP works when your team already uses Temporal and needs programmatic control during incidents. If you're just starting with Temporal or run fewer than 20 concurrent workflows, the web UI is faster. The buying call: if your on-call runbooks say 'cancel all workflows matching X', this MCP turns that into a single Switchy prompt.
How support engineers trace user issues through Temporal executions
A 3-person support team at a fintech startup fields tickets like 'my payment is stuck'. Each payment is a Temporal workflow; the engineer needs to see if it's running, stalled, or terminated. The count workflows and cancel workflow tools let support query by customer ID, check execution status, and safely cancel a stuck workflow without touching production code. The cooperative cancellation model means the workflow's cleanup handlers still run—refunds process, notifications send. This MCP is the right call when support needs read-write access to workflow state but shouldn't deploy code. If your workflows don't expose customer IDs in searchable attributes, or if support only needs read-only visibility, Temporal's built-in UI is enough. The threshold: if support escalates more than 5 workflow issues per week, this MCP pays off.
Batch resets for rolling out workflow logic fixes across live executions
A 10-person SaaS team ships a bug fix to a long-running subscription-renewal workflow. 800 customer workflows are mid-execution with the old logic; they need resetting to the fixed version. The batch reset tool lets an engineer preview the exact query ('WorkflowType=renewal AND Status=Running'), get approval from the team lead in Switchy's shared context, then reset all 800 in one operation. Each reset replays history with the new code, so side effects (like duplicate emails) are a real risk—the MCP's warning labels make that trade-off explicit. This works when your team has a staging environment to test resets and a clear rollback plan. If your workflows are stateless or you can wait for natural completion, skip the reset. The call: if deploying a workflow fix means manually resetting hundreds of executions, this MCP is the tool.
Frequently asked
What does the Temporal MCP let me do in Switchy?
It gives your AI agents direct control over Temporal workflows — cancel, terminate, reset, signal, or batch-update running executions without writing code. Agents can query workflow state, count executions by visibility filter, and trigger cooperative shutdowns or hard stops. Useful when you want an LLM to orchestrate long-running processes or respond to operational alerts by acting on workflows in real time.
Do I need admin access to connect Temporal?
You need an API key with at least Namespace Read and Workflow Write permissions. Batch operations — delete, reset, terminate — require elevated privileges because they're destructive and irreversible. If your Temporal Cloud account restricts API keys to read-only, you won't be able to use the cancel, signal, or update tools. Check your namespace IAM settings before connecting.
Can the MCP start new Temporal workflows?
No. The 49 tools focus on managing and querying existing workflow executions — cancel, terminate, reset, signal, count, update options. If you need to start workflows, use Temporal's native SDKs or the gRPC/HTTP API directly. The MCP is designed for operational control and observability, not workflow authoring or initial dispatch.
How is this different from calling Temporal's API myself?
You skip writing boilerplate: the MCP handles auth, pagination, visibility-query syntax, and batch-operation safety checks. An agent can say "cancel all stuck workflows in the payments namespace" and the MCP translates that into the correct API calls, previews the count, and executes. You trade fine-grained control for speed and natural-language orchestration inside Switchy.
Who on my team should connect this integration?
Whoever owns your Temporal Cloud account and can generate API keys with write permissions. Typically a platform engineer or SRE. Once connected, any Switchy user in your workspace can invoke the tools, so restrict access if junior team members shouldn't be able to terminate production workflows. The MCP doesn't isolate permissions per user.