Do I need an API key to use this World Time server?

No. This server uses the World Time API, which is a public keyless micro-service. You can start using it immediately without any manual configuration or signup processes.

Can I check the time based on my current location?

Yes. Using the `get_current_time` tool with the parameter 'ip', your agent will automatically infer your location from the network IP address and return the correct local time and timezone details.

How do I find the correct string for a specific timezone?

You can use the `list_available_timezones` tool. It will return a complete list of valid IANA timezone identifiers (like 'Asia/Tokyo' or 'Australia/Sydney') supported by the service.

World Time (Keyless) MCP Server for CrewAI 2 tools — connect in under 2 minutes

Name: World Time (Keyless)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 2 Tools Framework

Connect your CrewAI agents to World Time (Keyless) through the Vinkius — pass the Edge URL in the `mcps` parameter and every World Time (Keyless) 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="World Time (Keyless) Specialist",
    goal="Help users interact with World Time (Keyless) effectively",
    backstory=(
        "You are an expert at leveraging World Time (Keyless) 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 World Time (Keyless) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 2 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 World Time (Keyless) MCP Server

Connect to the World Time API and empower your AI agent with precise, synchronized time data through natural conversation. This server provides micro-service level access to atomic time across all IANA timezone regions without requiring any manual signups or complex API keys.

When paired with CrewAI, World Time (Keyless) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call World Time (Keyless) tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Precise Synchronization — Retrieve the exact current time for any valid IANA region (e.g., 'Europe/London' or 'America/New_York') with millisecond precision
Offset Discovery — Verify the current UTC offset and check whether a specific location is currently observing Daylight Saving Time (DST)
Timezone Browsing — List all supported timezone strings to ensure you are using the correct identifier for your requests
IP-Based Inference — Automatically retrieve the current local time based on the inferred location of the network IP address
Standardized Data — Access high-quality JSON responses including Unix timestamps, day of year, and week number for scheduling purposes
Global Coverage — Get reliable time data for any part of the world, from major cities to remote islands

The World Time (Keyless) MCP Server exposes 2 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 World Time (Keyless) to CrewAI via MCP

Follow these steps to integrate the World Time (Keyless) 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 2 tools from World Time (Keyless)

Why Use CrewAI with the World Time (Keyless) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with World Time (Keyless) 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 the 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

World Time (Keyless) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the World Time (Keyless) MCP Server delivers measurable value.

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

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

World Time (Keyless) MCP Tools for CrewAI (2)

These 2 tools become available when you connect World Time (Keyless) to CrewAI via MCP:

get_current_time

You can provide a timezone string (e.g. "America/Sao_Paulo") or use "ip" to infer from the network. Retrieves the exact current atomic time, UTC offset, and DST state for a specified timezone

list_available_timezones

Lists all valid timezone regions (e.g. Europe/London) supported by the World Time API

Example Prompts for World Time (Keyless) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with World Time (Keyless) immediately.

"What time is it in Tokyo right now?"

"Check the current time based on my IP."

"Is London currently in Daylight Saving Time?"

Troubleshooting World Time (Keyless) MCP Server with CrewAI

Common issues when connecting World Time (Keyless) 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

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

World Time (Keyless) + CrewAI FAQ

Common questions about integrating World Time (Keyless) 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.