Skip to content
Vinkius

Temporal Connector for AI agents.

7 live capabilities

Query and debug distributed workflows in Temporal Cloud natively.

Live agent request Temporal / Connector

Waiting for input…

AI Agent

Why people use Temporal

Temporal for Debugging Distributed Workflow Failures

This Connector lets you skip the navigation entirely. You just tell your AI client what's wrong, and it pulls the history or searches the visibility logs for you. You get the answer in seconds instead of minutes of clicking.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get instant, conversational access to your Temporal cluster data without leaving your workspace.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 5,900+ Connectors

  1. Real-world use case 01

    Failed Job Debugging

    An engineer asks, "Why did the InvoiceWorkflow fail?

  2. Real-world use case 02

    Production Incident Response

    An SRE asks for all running workflows in a specific namespace.

  3. Real-world use case 03

    Schedule Audit

    A platform team wants to know when the next backup runs.

Complete set · 7capabilities

The complete Temporal capability set.

These are the exact actions your AI can choose when you ask it to work with Temporal.

Capability set01 / 02

01—04

4 capabilities in this set.

Part of 7 available through Temporal.

  1. 01 Capability

    Get workflow history

    Pull the full sequence of events and activities for a specific workflow execution to find exactly where it failed.

  2. 02 Capability

    Get namespace details

    Check your current namespace's configurations, metadata, and retention periods in one go.

  3. 03 Capability

    Get workflow details

    Get the specific status and metadata for a single workflow run to see its current state.

  4. 04 Capability

    List schedules

    See all recurring workflows and their next scheduled execution times across your cluster.

Capability set02 / 02

05—07

3 capabilities in this set.

Part of 7 available through Temporal.

  1. 05 Capability

    List search attributes

    View the custom search attributes available in your namespace to understand your querying options.

  2. 06 Capability

    List workflows

    Get a high-level list of all workflow IDs, run IDs, and statuses in your namespace.

  3. 07 Capability

    Search workflows

    Run complex visibility queries to find specific runs based on status, type, or other attributes.

Set up in minutes

One URL. Then ask Temporal to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Temporal from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_EnU6gjOxc9KSHxcvKKIpGvDNCsHHJOBTVxTch47l/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it Temporal, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable Temporal for the conversation.

Where the request belongs

Work Temporal can move forward.

Built around the request

This is for the engineers who are tired of clicking through nested menus during a high-pressure incident. It's for the person who needs to know exactly why a job failed without manually correlating logs.

01

Software Engineer

Debugging failed workflow runs and pulling event histories during development.

02

Platform Engineer

Auditing namespace configurations and checking retention periods for compliance.

03

SRE

Querying complex visibility logs during active production incidents to identify bottlenecks.

Build the capability set

Add more capabilities.

Each Connector adds new actions and data without changing how you work.

Browse Connectors
Make (Workflow Automation) logo
01 7 capabilities

Make (Workflow Automation)

Manage workflow automation via Make. audit scenarios, track execution logs, and monitor data stores.

View Connector
Orkes Conductor logo
02 6 capabilities

Orkes Conductor

Orchestrate microservice workflows via Orkes Conductor. list definitions, track running executions, search workflow history, and inspect task states from any AI agent.

View Connector
Workflow Orchestrator Prover logo
03 1 capability

Workflow Orchestrator Prover

AI agents build fragile pipelines that fail silently, ignore rate limits, and double-process events. This prover enforces distributed systems discipline: mandatory dead-letter queues (DLQ), exponential backoff, stateful idempotency tracking, and secure credentials.

View Connector
Activepieces logo
04 32 capabilities

Activepieces

Automate workflows with Activepieces. manage flows, monitor executions, and handle app connections directly from your AI agent.

View Connector
Lindy (Autonomous AI Employees) logo
05 10 capabilities

Lindy (Autonomous AI Employees)

Manage autonomous AI employees via Lindy. trigger task runs, monitor reasoning logs, and audit app integrations.

View Connector
Trigger.dev (Background Tasks & Jobs) logo
06 19 capabilities

Trigger.dev (Background Tasks & Jobs)

Manage background tasks and jobs via Trigger.dev. trigger tasks, monitor runs, manage schedules, and configure environment variables directly from your AI agent.

View Connector

Bring your own AI

Change the model, client or framework. Keep Temporal connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about Temporal.

The practical details behind the request, access and result.

Can I use the Temporal MCP to debug failed workflows in Claude or Cursor?

Yes. This Connector allows your AI client to query your Temporal cluster directly. You can ask it to find specific failed runs or pull their full history without leaving your editor.

Does the Temporal MCP work with self-hosted clusters?

Yes, it works with both Temporal Cloud and self-hosted clusters. You just need to provide your Temporal Address and the correct API credentials.

How does the Temporal MCP help with production incidents?

It speeds up incident response by letting you query visibility logs and list active workflows using natural language. This eliminates the need to navigate complex UIs during a crisis.

Can the Temporal MCP check my namespace configurations?

Yes. You can ask your agent to retrieve namespace details, such as retention periods and metadata, to ensure your environment is configured correctly.

Will the Temporal MCP show me my recurring cron jobs?

Yes. It can list all workflow schedules and even tell you the predicted next execution time for your recurring tasks.

Do I need to write any code to use the Temporal MCP?

No code is required. Once you subscribe and provide your credentials, you can interact with your Temporal data through plain English conversation with your AI agent.

Can my AI agent debug a failed Temporal workflow run directly?

Yes. Instead of browsing the Temporal UI to manually dissect the execution, feed the workflow ID directly to your AI agent. It can seamlessly fetch the entire event history, identify the exact panic line or activity timeout, and immediately suggest code fixes within your IDE.

How complex can the visibility searches be via natural language?

Very complex. Because your agent understands your codebase, you can ask 'Find all workflows of type ProcessPayment that failed in the last 2 hours'. The agent formulates the perfect SQL-like syntax for the backend, parses the matching pages, and surfaces exactly which transactions failed.

Can it read scheduled jobs and Cron jobs configurations inside Temporal?

Absolutely. You can request a list of all active schedules mapped to your namespace. Your agent unpacks JSON configurations, showing definitions of workflow recurrence, enabling you to detect missing crons without interrupting your workflow.

One connection away

Give your agent a direct line to Temporal.

Connect Temporal once. Keep it beside 5,900+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available