LabscoConnect MCP ↗
PLUGIN / TEMPORALIOOFFICIAL

Temporal

Temporal's own plugin for coding assistants: one install gives Claude Code, Cursor or Codex four Temporal skills, from writing the code to running it on Temporal Cloud.

What gets installed: 4 skills

Skills

All four arrive together with one install of the plugin.

Installed separately, not part of this plugin: Temporal Cloud, for connection and sign-in problems

temporal-developer

Temporal runs the parts of an app that must not be lost halfway through — a payment, a nightly batch, an approval that waits a week. This is the working reference for writing and fixing that code in seven languages, down to using it as an ordinary background-job queue.

temporal-ops

Looks after a running Temporal setup, on Temporal Cloud or your own servers, through Temporal's command-line tools: namespaces, API keys and certificates, capacity, and bulk actions on workflows. Given an error, it checks each layer from the network up to your code and names the cause with a confidence score from 1 to 10. It is a public preview, so its coverage may still change.

temporal-serverless

Temporal can start a Worker, the program that runs your Temporal code, on AWS Lambda only when there is work, and stop it afterwards. This skill writes that Worker, deploys it to your AWS account and connects it to Temporal, or works out why an existing one is not picking up tasks. It is a public preview, so its coverage may still change.

temporal-cloud-setup

A guided first run on Temporal Cloud, done for you: the assistant installs Temporal's command-line tool, signs you in, creates a namespace and an API key, then downloads a sample money-transfer app in your language and runs it. It ends by breaking a transfer on purpose so you can watch Temporal recover it.

Labsco Summary

Three of the four skills start only when you type their command, and Cloud Setup creates billable resources in your Temporal Cloud account. Show

Three of the four wait to be called.

The Developer skill is picked up by the assistant on its own whenever the work calls for it. The other three never start by themselves; you type their command in the chat:

  • /temporal:temporal-ops for looking after a running Temporal setup
  • /temporal:temporal-serverless for Workers on AWS Lambda
  • /temporal:temporal-cloud-setup for a first run on Temporal Cloud

The plugin's copy of the Developer skill is an older release than the one in its own repository, which has changed since.

Cloud Setup works in your own account.

Cloud Setup creates a real namespace and API key in your Temporal Cloud account, which may cost money. The skill removes neither when it finishes; the key expires on its own after about a day.

It has to run in a terminal on your own computer with open internet access, so Codex's default sandbox will not do. On a Mac it installs Temporal's prerelease command-line tool through Homebrew.

Delete the namespace in Temporal Cloud once you no longer need it.

02 INSTALL

One plugin, three coding assistants.
Restart yours after installing.

CLAUDE CODE

Add the marketplace, then install the plugin

Typed inside the agent's own prompt, not in a terminal. The marketplace is called temporal-marketplace, which is the part after the @.

  1. /plugin marketplace add temporalio/claude-temporal-plugin
  2. /plugin install temporal@temporal-marketplace

CURSOR

Type one line in Cursor's agent chat

You can also install the Temporal plugin from the Cursor Marketplace instead.

  1. /add-plugin temporal

CODEX

Pick Temporal from Codex's plugin list

In the Codex CLI: run /plugins, choose the OpenAI Curated marketplace, search for temporal and install it. In the Codex app: open the plugins menu, search for temporal and click + (Add to Codex).

  1. /plugins