How to connect Temporal to Claude

Connect Claude Web, Desktop and Cowork to Temporal MCP. Start temporal workflow to process order 12345, list running workflows for customer acme corp, and more using natural language, with authentication handled for you.

Temporal logoTemporal
Api Key

Temporal is a cloud-native workflow orchestration platform for building reliable distributed applications. It ensures workflows run reliably, scale automatically, and recover from failures.

63 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Temporal account to Claude via Composio Connect, enabling it to start Temporal workflow to process order 12345, list running workflows for customer ACME Corp, cancel workflow execution with workflowId abc-789, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Temporal with

Connecting Temporal to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Temporal account

Back in Claude, ask it to connect to Temporal or give it any Temporal-related task.

For example, ask Claude to:

  • "Start Temporal workflow to process order 12345"
  • "List running workflows for customer ACME Corp"
  • "Cancel workflow execution with workflowId abc-789"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Temporal account is ready to use.

What is the Temporal Claude Connector, and what's possible with it?

The Temporal MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Temporal account. It provides structured and secure access to your namespaces, workflows, schedules, workflow rules, batch operations, regions, and export sinks, so your agent can inspect workflows, manage schedules, control workflow executions, monitor operations, and review cloud resources on your behalf.

  • Workflow search and inspection: Have your agent find active or archived workflows, check their status and pending work, count matching executions, and review event history.
  • Workflow execution control: Direct your agent to cancel individual workflows or signal, reset, terminate, delete, and update options across selected workflows in batches.
  • Schedule management: Let the agent create, inspect, list, pause, unpause, trigger, backfill, or delete schedules, and preview their matching run times.
  • Namespace and region operations: Instruct your agent to review namespaces, capacity, assignments, and available regions, or manage namespace moves, regional failovers, and deletion when needed.
  • Rules, exports, and operation tracking: Have your agent manage workflow rules and history export sinks, then track batch jobs and asynchronous cloud operations through completion.

Troubleshooting

1. Why does Claude not use the Composio connector for Temporal?

The connector can show as connected, but Claude must use it in each Temporal conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Temporal again.

2. Why does Claude show an MCP server error before Temporal connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Temporal.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Temporal.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Temporal authorization link not work?

The Composio connector is one server. Your Temporal account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Temporal connection.
  • Composio creates a fresh Temporal authorization link.
  • Open that link in your browser and finish the Temporal sign-in.

4. Why do Temporal actions fail after they worked before?

The Temporal connection can expire or lose permission.

  • Ask Claude to inspect the Temporal connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Temporal account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Temporal.
  • If the action still fails with a permission error, check that the connected account has that permission in Temporal itself.

5. How do I switch to a different Temporal account?

Claude can manage the Temporal connection for you.

  • Ask Claude to disconnect or delete the current Temporal account.
  • Ask Claude to connect Temporal again.
  • Open the new Composio authorization link for Temporal.
  • Sign in with the other Temporal account in the browser.
  • After the account connects, ask Claude to retry the Temporal task.

6. Why is my Temporal connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Temporal connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Temporal tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Temporal.
TOOLS

Supported Tools

Every Temporal action and event your agent gets out of the box.

Batch Cancel Workflows

Request cancellation of selected Temporal Workflows.

Batch Delete Workflows

WARNING: Permanently delete selected Temporal Workflow Executions and their Event Histories.

Batch Reset Workflows

WARNING: Irreversibly reset selected Temporal Workflows.

Batch Signal Workflows

Send a named Signal to selected Temporal Workflows.

Batch Terminate Workflows

WARNING: Irreversibly terminate selected Temporal Workflows immediately; Workflow cleanup code does not run.

Batch Update Workflow Options

Update typed execution options on selected Temporal Workflows.

Cancel Workflow

Irreversibly request cooperative cancellation of a running Temporal Workflow Execution.

Count Schedules

Return an approximate count of Temporal Schedules matching a Schedule Visibility query, including grouped counts when requested.

Count Workflows

Return an approximate count of Workflow Executions matching a Temporal Visibility query, including supported grouped counts.

Create and Apply Workflow Rule

Create a Namespace-wide Temporal Workflow Rule and immediately start a batch job applying it to matching currently running Workflows.

Create Export Sink

Create a persistent Temporal Cloud Workflow History export sink asynchronously.

Create Schedule

Create a Temporal Schedule that starts a configured Workflow on cron, interval, calendar, or structured-calendar times.

Create Workflow Rule

Create a Namespace-wide Temporal Workflow Rule that can pause matching Activities when its trigger occurs.

Delete Export Sink

Delete a Temporal Cloud Workflow History export sink asynchronously.

Delete Namespace

Permanently and irreversibly delete a Temporal Cloud Namespace and all of its Workflow data asynchronously.

Delete Schedule

Permanently delete one Temporal Schedule from a Namespace.

Delete Workflow Rule

Permanently delete one configured Temporal Workflow Rule from a Namespace.

Describe Batch Operation

Return progress, state, selection query, type, and failure counts for one batch operation in an authorized Temporal Cloud Namespace.

Describe Namespace

Return one Temporal Cloud Namespace's configuration, resource version, routing endpoints, state, limits, and capacity.

Describe Schedule

Return the complete current definition, state, execution information, Memo, Search Attributes, and conflict token for one Temporal Schedule.

Describe Workflow

Return configuration, status, pending work, callbacks, and child state for one Workflow Execution in an authorized Temporal Cloud Namespace.

Describe Workflow Rule

Return one configured Temporal Workflow Rule, including its trigger, Visibility query, actions, expiration, creation metadata, and description.

Fail Over Namespace Region

Switch a multi-region Temporal Cloud Namespace's active region asynchronously.

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.

Get Namespace Capacity

Return a Temporal Cloud Namespace's capacity mode, available limits, and seven-day actions-per-second statistics.

Get Cloud Region

Return details for one Temporal Cloud region, including its cloud provider, provider-specific identifier, and human-readable location.

Get Workflow History

Return one page of a Temporal Workflow Execution's Event History in forward or reverse order.

List Archived Workflows

Return one page of archived Workflow Executions matching an exact Temporal Visibility query.

List Batch Operations

Return one page of batch operations in an authorized Temporal Cloud Namespace.

List Export Sinks

Return one page of Workflow History export sinks configured on a Temporal Cloud Namespace.

List Namespace Assignments

Return one page of users, User Groups, or Service Accounts assigned to a Temporal Cloud Namespace.

List Namespaces

Return one page of Temporal Cloud Namespaces visible to the API-key identity, optionally filtered by name or Project.

List Cloud Regions

List currently available Temporal Cloud regions for Namespace placement.

List Schedule Matching Times

List times within a required start-to-end range that match one Temporal Schedule's timing specification.

List Schedules

Return one filtered page of Temporal Schedules in an authorized Temporal Cloud Namespace.

List Workflow Rules

Return one page of Workflow Rules configured for an authorized Temporal Cloud Namespace.

List Workflows

Search one page of Workflow Executions in an authorized Temporal Cloud Namespace using Temporal Visibility query syntax.

Move Namespace To Project

Move a Temporal Cloud Namespace to another Project asynchronously.

Patch Schedule

Apply targeted changes to a Temporal Schedule without replacing its definition: pause or unpause it, trigger one immediate action, or backfill historical times.

Pause Workflow

Pause one Temporal Workflow Execution.

Query Workflow

Run a synchronous, read-only Query handler against one Temporal Workflow Execution.

Register Namespace

Create a billable, persistent Temporal Cloud Namespace asynchronously and return its full Namespace ID and operation ID.

Remove Namespace Access

Remove one user's, user group's, or service account's direct permission on a Temporal Cloud Namespace by setting PERMISSION_UNSPECIFIED.

Rename Custom Search Attribute

Rename one custom Search Attribute in a Temporal Cloud Namespace asynchronously.

Replace Workflow

Replace a running Workflow Execution with a new execution using the same Workflow ID.

Reset Workflow

WARNING: Irreversibly reset a Temporal Workflow to a selected Workflow Task event.

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.

Signal With Start Workflow

Atomically signal a running Temporal Workflow or start and signal it when absent.

Signal Workflow

Send an asynchronous Signal to one running Temporal Workflow Execution.

Start or Get Workflow

Start a Workflow Execution, or return the already-running execution when the Workflow ID conflicts.

Start Workflow

Start a new Workflow Execution in an authorized Temporal Cloud Namespace.

Stop Batch Operation

Request that Temporal stop an in-progress batch operation.

Terminate Workflow

Immediately and irreversibly terminate one Temporal Workflow Execution.

Trigger Workflow Rule

Trigger an existing configured Temporal Workflow Rule against one Workflow Execution.

Unpause Workflow

Resume a paused Temporal Workflow Execution.

Update Export Sink

Update an existing Temporal Cloud Workflow History export sink asynchronously using optimistic concurrency.

Update Namespace

Update a Temporal Cloud Namespace specification asynchronously using the latest resource version for optimistic concurrency.

Update Namespace Tags

Upsert or permanently remove tags on a Temporal Cloud Namespace asynchronously; removed tags no longer exist on the Namespace.

Update Schedule

Fully replace an existing Temporal Schedule's spec, Workflow-start action, policies, and state.

Update Workflow

Send a durable Update to one Temporal Workflow Execution and wait for the requested lifecycle stage.

Update Workflow Options

Update selected options on one Temporal Workflow Execution using an exact protobuf FieldMask.

Validate Export Sink

Validate a Temporal Cloud Workflow History export sink configuration.

FAQ

Frequently asked questions

With a standalone Temporal MCP server, the agents and LLMs can only access a fixed set of Temporal tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Temporal and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Temporal tools.

Yes, absolutely. You can configure which Temporal scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Temporal data and credentials are handled as safely as possible.

Start with Temporal.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Temporal tool your agent needs.Free to start.

Start building