How do I find my TimezoneDB API Key?

Log in to your [**TimezoneDB account**](https://timezonedb.com/register), and you will find your API Key on the main page. Copy and paste it below.

Does the agent support searching by city?

While the primary tools use zone strings or coordinates, you can use `list_timezones` to find the correct zone name for a specific country.

Can the agent check if DST is active?

Yes. The `get_dst_status` tool returns a boolean value identifying if daylight saving time is currently being observed in the specified zone.

TimezoneDB MCP Server for CrewAI 5 tools — connect in under 2 minutes

Name: TimezoneDB
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 5 Tools Framework

Connect your CrewAI agents to TimezoneDB through Vinkius, pass the Edge URL in the `mcps` parameter and every TimezoneDB tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="TimezoneDB Specialist",
    goal="Help users interact with TimezoneDB effectively",
    backstory=(
        "You are an expert at leveraging TimezoneDB 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 TimezoneDB "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 5 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 TimezoneDB MCP Server

Empower your AI agent to orchestrate your entire global time and timezone research workflow with TimezoneDB, the authoritative source for world clock data. By connecting TimezoneDB to your agent, you transform complex offset lookups into a natural conversation. Your agent can instantly retrieve current time for any zone, audit daylight saving statuses, and identify regional time variations without you ever touching a manual converter. Whether you are planning international calls or building global scheduling systems, your agent acts as a real-time time consultant, ensuring your data is always precise and synchronized.

When paired with CrewAI, TimezoneDB becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call TimezoneDB 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

Time Auditing — Retrieve the exact current time for over 400 timezones and maintain a clear view of global offsets.
Location Oversight — Query timezone details based on geographic coordinates to understand local time patterns instantly.
Zone Discovery — List all supported timezones by country to identify regional variations and abbreviations.
DST Intelligence — Check if daylight saving time is currently active for any zone to assist in precise scheduling.
Spatial Discovery — Retrieve latitude and longitude metadata for specific zones to maintain spatial context.

The TimezoneDB MCP Server exposes 5 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 TimezoneDB to CrewAI via MCP

Follow these steps to integrate the TimezoneDB 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 5 tools from TimezoneDB

Why Use CrewAI with the TimezoneDB MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with TimezoneDB 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

TimezoneDB + CrewAI Use Cases

Practical scenarios where CrewAI combined with the TimezoneDB MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries TimezoneDB 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 TimezoneDB, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain TimezoneDB 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 TimezoneDB against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

TimezoneDB MCP Tools for CrewAI (5)

These 5 tools become available when you connect TimezoneDB to CrewAI via MCP:

check_api_status

Check if the TimezoneDB API is operational

get_dst_status

Check if daylight saving time is currently active for a zone

get_time_by_location

Get current time for specific geographic coordinates

get_time_by_zone

g., "America/New_York. Get current time and details for a specific timezone (e.g., "America/New_York")

list_timezones

List all supported timezones, optionally filtered by country

Example Prompts for TimezoneDB in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with TimezoneDB immediately.

"What is the current time in 'Asia/Tokyo' using TimezoneDB?"

"Check time for latitude 40.7128, longitude -74.0060."

"List all timezones in 'Brazil'."

Troubleshooting TimezoneDB MCP Server with CrewAI

Common issues when connecting TimezoneDB to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

TimezoneDB + CrewAI FAQ

Common questions about integrating TimezoneDB MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard 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?

Yes. Each agent has its own 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?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using 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)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.