temporal

This MCP server integrates with Temporal to expose workflow history and related resources via MCP endpoints. The primary tool exposed is workflow_history, which retrieves the execution history for a given Temporal workflow. To use it, you provide the tool name and the required identifiers for the workflow and run, and the server will fetch and return the history from the Temporal backend. There is also a resource bridge at test://resource that serves as a guide to understanding workflow histories within this MCP server context. To interact with the server, ensure the Temporal address and namespace are correctly configured via environment variables, then run the server and issue JSON requests to the MCP API describing the tool or resource you want to access.

Prerequisites:

• Go toolchain (Go 1.20+)
• Access to a Temporal service (or a local Temporal instance)
• Network access to Temporal from where you run the MCP server

Steps:

1. Install Go if not already installed

   • On macOS: brew install go
   • On Windows/Linux: follow https://golang.org/dl/

2. Clone the MCP Temporal server repository and navigate to it

3. Install dependencies and run the server

   • Use the command that starts the server as described below:

# Run the MCP Temporal server (from repository root)
GO111MODULE=on go run cmd/server/main.go

4. Verify the server starts and listens on the configured port (default 8080). If you need to customize Temporal connection details, set TEMPORAL_ADDRESS, TEMPORAL_NAMESPACE, and PORT environment variables before starting. For example:

export TEMPORAL_ADDRESS=localhost:7233
export TEMPORAL_NAMESPACE=default
export PORT=8080
GO111MODULE=on go run cmd/server/main.go

5. Test a basic workflow_history request once the server is running (see how_to_use for example payloads).

Notes:

• Ensure Temporal is reachable from the environment running this MCP server. Network ACLs or firewall rules may block the Temporal gRPC endpoint.
• If Temporal authentication is required, you may need to extend env configuration to pass credentials or TLS settings depending on your Temporal deployment.
• The server defaults to port 8080 if PORT is not provided. You can override this by exporting PORT before starting the server.
• The test://resource endpoint serves as a guidance resource for understanding workflow histories; you can request it exactly as shown in the README example to fetch the guide content.