⏰🧠 Temporal-MCP Server

Created By
Mocksia year ago
Empowering AI with Workflow Orchestration
Overview

What is Temporal-MCP?

Temporal-MCP is a server that connects AI assistants with Temporal workflows, allowing users to manage complex backend processes through simple, chat-driven commands. It enables triggering stateful processes without the need for extensive coding.

How to use Temporal-MCP?

To use Temporal-MCP, set up a Temporal server, build the MCP server from the source code, define your workflows in a configuration file, and interact with the workflows using natural language through an AI assistant like Claude.

Key features of Temporal-MCP?

  • Automatic Discovery: Explore available workflows with rich metadata.
  • Seamless Execution: Initiate complex processes with a single chat message.
  • Real-time Monitoring: Track progress and receive live updates.
  • Performance Optimization: Smart caching for quick responses.
  • AI-Friendly Descriptions: Clear purpose fields for both humans and machines.

Use cases of Temporal-MCP?

  1. Automating financial transactions between accounts.
  2. Managing workflows that require human approval.
  3. Testing various scenarios in workflow execution.

FAQ from Temporal-MCP?

  • What is the purpose of Temporal-MCP?

It simplifies the orchestration of workflows for AI assistants, making it easier to manage complex tasks.

  • Is there a specific programming language required?

Yes, Temporal-MCP is built using Go, and requires Go 1.21 or higher.

  • Can I use it with any AI assistant?

Yes, it is designed to work with any MCP-enabled AI assistant, such as Claude.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Mocksi
Star
13
Language
Go
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago