Temporal MCP Server for CrewAI 7 tools — connect in under 2 minutes
Connect your CrewAI agents to Temporal through Vinkius, pass the Edge URL in the `mcps` parameter and every Temporal tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Temporal Specialist",
goal="Help users interact with Temporal effectively",
backstory=(
"You are an expert at leveraging Temporal tools "
"for automation and data analysis."
),
# Your Vinkius token. get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in Temporal "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 7 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Temporal MCP Server
Connect your Temporal Cloud (or self-hosted) cluster to any AI agent and bring the power of durable execution directly into your IDE or chat via natural conversation.
When paired with CrewAI, Temporal becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Temporal tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
What you can do
- Workflows & Executions — List, filter, and inspect active, running, or completed workflow executions
- Workflow History — Retrieve the complete sequence of events, activities, and signals to debug failures
- Visibility Search — Run complex SQL-like queries using Temporal Visibility syntax to find specific runs
- Namespace Details — Check retention periods, configurations, and metadata of your operational namespace
- Schedules & Cron — Browse all recurring workflows and predict the next execution schedules
The Temporal MCP Server exposes 7 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Temporal to CrewAI via MCP
Follow these steps to integrate the Temporal MCP Server with CrewAI.
Install CrewAI
Run pip install crewai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
Customize the agent
Adjust the role, goal, and backstory to fit your use case
Run the crew
Run python crew.py. CrewAI auto-discovers 7 tools from Temporal
Why Use CrewAI with the Temporal MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Temporal through the Model Context Protocol.
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Temporal + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Temporal MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Temporal for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries Temporal, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Temporal tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries Temporal against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Temporal MCP Tools for CrewAI (7)
These 7 tools become available when you connect Temporal to CrewAI via MCP:
get_namespace_details
Retrieves information about the current namespace
get_workflow_details
Retrieves details for a specific workflow execution
get_workflow_history
Retrieves the event history for a workflow execution
list_schedules
Lists all workflow schedules
list_search_attributes
Lists custom search attributes available in the namespace
list_workflows
Returns workflow IDs, run IDs, and statuses. Lists all workflow executions in the configured namespace
search_workflows
g., WorkflowType="MyType" AND Status="Running"). Search workflows using Temporal Visibility Query syntax
Example Prompts for Temporal in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Temporal immediately.
"Show me the last 5 workflows that failed or panicked in the default namespace."
"Explain the exact execution history for workflow 'GenerateInvoice-102'."
"List all active schedules and tell me when the database backup is due."
Troubleshooting Temporal MCP Server with CrewAI
Common issues when connecting Temporal to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Temporal + CrewAI FAQ
Common questions about integrating Temporal MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.Can different agents in the same crew use different MCP servers?
mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.What happens when an MCP tool call fails during a crew run?
Can CrewAI agents call multiple MCP tools in parallel?
process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.Can I run CrewAI crews on a schedule (cron)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Temporal with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Temporal to CrewAI
Get your token, paste the configuration, and start using 7 tools in under 2 minutes. No API key management needed.