Temporal Continuity

io.github.VRhodes68Published by GitHub account VRhodes68v0.1.1Updated Oct 24, 2026

Local MCP adapter connecting AI clients to the hosted Temporal Continuity API.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Local stdio MCP adapter that connects AI clients to the hosted Temporal Continuity API using a customer API key and tenant IDs.

What you can do
  • Acts as a bridge between an AI client and the hosted Temporal Continuity API.
  • No tools are listed in the manifest, so the specific actions available depend on what the remote API exposes.
  • Configuration is scoped to one tenant: an environment, organization and project are supplied as environment variables.
When to use it
Worth adding if you already use Temporal Continuity and want an AI assistant on your desktop to reach your hosted workspace through a local adapter rather than a direct remote connection.
Requirements
Runs as a local process over stdio, installed from the npm package temporal-continuity-mcp (Node.js runtime). Requires a Temporal Continuity customer API key plus a base URL and tenant environment, organization and project IDs, all set as environment variables. Network access to the Temporal Continuity endpoint is needed.
Before you install
The API key is a secret passed via TEMPORAL_CONTINUITY_API_KEY; keep it out of shared configuration and logs. All requests go to the third-party Temporal Continuity service, so data you ask the assistant to handle is sent there. The manifest lists no tools, so review what the adapter can read or change before use.

Installation

In SourceWeft

  1. Open Temporal Continuity in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestOct 15, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.