bechols/temcp

temcp: Temporal Cloud MCP Server

An MCP (Model Context Protocol) server that exposes Temporal Cloud operations as tools for AI assistants.

What you can do with it

• Learn about your Cloud environment
  • "How are my namespaces configured?"
  • "What does Jane Doe have access to?"
• Directly edit Cloud resources
  • "Create namespace-foo in aws us west with 1 day retention"
  • "Give service-account-1 access to namespace-foo"
  • "Add an API key for service-account-1"
• Update application code to work with your Cloud resources
  • "Make this Temporal project work with my Cloud account"

Demo

https://github.com/user-attachments/assets/fdf0b7b5-ca4d-4059-835e-77d30b1a212f

What's happening?

Starting from a simple Temporal project (not set up for Cloud), temcp helps Claude Code create the Temporal Cloud resources (namespace, service account access, API key) needed to run the project, and it updates the actual application code to connect to Cloud with the newly created credentials.

Setup before the video:

1. Clone https://github.com/temporalio/money-transfer-project-template-go/
2. Add temcp to Claude Code (instructions below)

Prompt given to Claude Code:

I want to use this repo with Temporal Cloud. Create a namespace, add a service account, and generate an API key. Use that plus the connection info tool to update the workflow and worker to connect to Cloud.

Use with Claude Code

claude mcp add temporal-cloud /path/to/mcp-server -e TEMPORAL_CLOUD_API_KEY="your-api-key"    

Use with Cursor

Configure .cursor/mcp.json:

{
  "mcpServers": {
    "temporal-cloud": {
      "command": "/path/to/mcp-server",
      "args": [],
      "env": {
        "TEMPORAL_CLOUD_API_KEY": "your-api-key"
      }
    }
  }
}

Use with MCP Inspector

1. Export your API key:

   export TEMPORAL_CLOUD_API_KEY="your-temporal-cloud-api-key"
   

2. Launch Inspector

   npx @modelcontextprotocol/inspector ./mcp-server
   

3. Open the URL provided by the inspector (e.g., http://localhost:6274/?MCP_PROXY_AUTH_TOKEN=tokenhash)

4. Click "Connect"

5. Navigate to the "Tools" tab to test all tools interactively

Building the MCP Server

go build -o mcp-server ./cmd/mcp-server

Test with CLI

./test_mcp

Available Tools

User Info:

• temporal_get_user - Get user details by ID
• temporal_list_users - List users

Account Access Info:

• temporal_get_account_access - Get a user's account-level access role (owner, admin, developer, finance_admin, read)

API Key Creation:

• temporal_create_api_key - Create a new API key for a user or service account

Namespace Access Management:

• temporal_get_user_namespace_access - Get a user's access level for a specific namespace
• temporal_set_user_namespace_access - Set or update a user's access level for a specific namespace

Namespace Management:

• temporal_get_namespace - Get namespace details by name
• temporal_list_namespaces - List namespaces
• temporal_create_namespace - Create a new namespace (defaults to API key auth enabled)
• temporal_update_namespace - Update an existing namespace
• temporal_delete_namespace - Delete a namespace

Region Availability:

• temporal_get_region - Get region details by ID
• temporal_list_regions - List all available regions

Async Operations:

• temporal_get_async_operation - Get async operation status
• temporal_wait_for_operation - Wait for async operation completion

Service Account Management:

• temporal_list_service_accounts - List Temporal Cloud service accounts
• temporal_create_service_account - Create a new service account with namespace access
• temporal_get_service_account_namespace_access - Get namespace access permissions for a service account
• temporal_set_service_account_namespace_access - Set namespace access permissions for a service account

Cloud Connection Info:

• temporal_cloud_connection_info - How to configure connections to Temporal Cloud

Export Processing: (untested as of July 2)

• temporal_process_export - Process exported workflow history files
• temporal_analyze_export - Analyze exported workflows and extract summaries

Note: per the MCP spec, the read-only tools should be resources. Everything's implemented as a tool because Cursor only supports tools for now.

Based on https://github.com/temporalio/cloud-samples-go

Uses https://github.com/mark3labs/mcp-go