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.

Temporal MCP Server for VS Code Copilot 7 tools — connect in under 2 minutes

Name: Temporal
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 7 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Temporal and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "temporal": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Temporal MCP Server

Connect your Temporal Cloud (or self-hosted) cluster to any AI agent and bring the power of durable execution directly into your IDE or chat via natural conversation.

GitHub Copilot Agent mode brings Temporal data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Workflows & Executions — List, filter, and inspect active, running, or completed workflow executions
Workflow History — Retrieve the complete sequence of events, activities, and signals to debug failures
Visibility Search — Run complex SQL-like queries using Temporal Visibility syntax to find specific runs
Namespace Details — Check retention periods, configurations, and metadata of your operational namespace
Schedules & Cron — Browse all recurring workflows and predict the next execution schedules

The Temporal MCP Server exposes 7 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Temporal to VS Code Copilot via MCP

Follow these steps to integrate the Temporal MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Temporal

Ask Copilot: "Using Temporal, help me..." — 7 tools available

Why Use VS Code Copilot with the Temporal MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Temporal through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Temporal + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Temporal MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Temporal MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect Temporal to VS Code Copilot via MCP:

get_namespace_details

Retrieves information about the current namespace

get_workflow_details

Retrieves details for a specific workflow execution

get_workflow_history

Retrieves the event history for a workflow execution

list_schedules

Lists all workflow schedules

list_search_attributes

Lists custom search attributes available in the namespace

list_workflows

Returns workflow IDs, run IDs, and statuses. Lists all workflow executions in the configured namespace

search_workflows

g., WorkflowType="MyType" AND Status="Running"). Search workflows using Temporal Visibility Query syntax

Example Prompts for Temporal in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Temporal immediately.

"Show me the last 5 workflows that failed or panicked in the default namespace."

"Explain the exact execution history for workflow 'GenerateInvoice-102'."

"List all active schedules and tell me when the database backup is due."

Troubleshooting Temporal MCP Server with VS Code Copilot

Common issues when connecting Temporal to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Temporal + VS Code Copilot FAQ

Common questions about integrating Temporal MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.