T

MCP Entry

Temporal MCP

Exposes Temporal workflow execution state, namespace management, and search attributes to AI agents for debugging long-running business processes. Agents can inspect workflow history, debug stuck executions, and trigger new workflow runs. Supports self-hosted and Temporal Cloud deployments.

Category Developer Tools
Install npm
Runtime Node.js
workflowsorchestrationdev

Use cases

  • Developer debugs stuck workflow by examining execution history and events
  • SRE monitors long-running business transactions across workflow executions
  • Operations team triggers manual workflow runs for data reconciliation
  • Engineer investigates failed activities by inspecting retry history
  • Product manager checks workflow metrics for process optimization

Key features

  • Claude Desktop
  • Cursor
  • VS Code

Frequently Asked Questions

What Temporal namespaces can agents access?
Agents can access namespaces based on their Temporal server permissions. Configure namespace access in your Temporal server or Temporal Cloud settings.
Can agents start new workflow executions?
Yes, with appropriate permissions agents can signal, query, and start new workflow executions. They can also cancel or terminate running workflows.
Does it support Temporal Cloud?
Yes, the MCP works with Temporal Cloud (cloud.temporal.io) as well as self-hosted Temporal clusters. Use mTLS or API key authentication.

Related

Related

3 Indexed items