Loading…
Manage Temporal workflows, schedules, namespaces, task queues, and workflow execution history from MCP clients.
Temporal is an MCP server entry in ChatHome Skills, sourced from Docker MCP Registry and scored 100/100. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding Temporal to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
docker run -i --rm mcp/temporalReview the upstream source before running this command.
{
"raw": "name: temporal\nimage: mcp/temporal\ntype: server\nmeta:\n category: devops\n tags:\n - temporal\n - workflow\n - orchestration\n - devops\nabout:\n title: Temporal\n description: Manage Temporal workflows, schedules, namespaces, task queues, and workflow execution history from MCP clients.\n icon: https://media.licdn.com/dms/image/v2/D560BAQG2k4od1BnFYw/company-logo_200_200/company-logo_200_200/0/1719946312124/temporal_technologies_logo?e=2147483647&v=beta&t=MFaqPo93l6qp8Dj0NrAdWyIk3izLBhN1i0WCBf-yVFs\nsource:\n project: https://github.com/GethosTheWalrus/temporal-mcp\n commit: 1965fe11d6f3d0aefb95c145b82f724ec26003cb\nconfig:\n description: Configure the connection to Temporal. For a local Temporal service running on the host, use host.docker.internal:7233. For Temporal Cloud, use your namespace endpoint and provide an API key or mounted mTLS certificate paths.\n secrets:\n - name: temporal.api_key\n env: TEMPORAL_API_KEY\n example: <TEMPORAL_API_KEY>\n description: Optional Temporal Cloud API key. TLS is enabled automatically when this is set.\n env:\n - name: TEMPORAL_HOST\n example: host.docker.internal:7233\n value: \"{{temporal.temporal_host}}\"\n description: Temporal frontend host and port.\n - name: TEMPORAL_NAMESPACE\n example: default\n value: \"{{temporal.temporal_namespace}}\"\n description: Temporal namespace to connect to.\n - name: TEMPORAL_TLS_ENABLED\n example: \"false\"\n value: \"{{temporal.temporal_tls_enabled}}\"\n description: Force TLS on or off. Leave false for local development unless your Temporal endpoint requires TLS.\n - name: TEMPORAL_TLS_CLIENT_CERT_PATH\n example: /certs/client.pem\n value: \"{{temporal.temporal_tls_client_cert_path}}\"\n description: Optional path inside the container to an mTLS client certificate.\n - name: TEMPORAL_TLS_CLIENT_KEY_PATH\n example: /certs/client.key\n value: \"{{temporal.temporal_tls_client_key_path}}\"\n description: Optional path inside the container to an mTLS client private key.\n parameters:\n type: object\n properties:\n temporal_host:\n type: string\n description: Temporal frontend host and port.\n default: host.docker.internal:7233\n temporal_namespace:\n type: string\n description: Temporal namespace to connect to.\n default: default\n temporal_tls_enabled:\n type: string\n description: Whether to force TLS for the Temporal connection.\n default: \"false\"\n temporal_tls_client_cert_path:\n type: string\n description: Optional path inside the container to an mTLS client certificate.\n temporal_tls_client_key_path:\n type: string\n description: Optional path inside the container to an mTLS client private key.\n required:\n - temporal_host\n - temporal_namespace\n",
"path": "servers/temporal/server.yaml"
}