How to Use the TimezoneDB MCP in CrewAI

Q: Does CrewAI support selective tool exposure for the TimezoneDB MCP Server?

Yes. Use MCPServerHTTP with a toolfilter to expose only specific tools to certain agents. This prevents your researcher agent from calling administration endpoints unnecessarily.

Delegate coordinate lookups and offset tracking across collaborative agent teams with the TimezoneDB MCP Server for CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect TimezoneDB MCP to CrewAI

Create your Vinkius account to connect TimezoneDB to CrewAI — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup TimezoneDB with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Automated Team Coordination in CrewAI

This MCP Server enables your operations crew to dynamically schedule tasks across global boundaries using `get_time_by_location` to resolve local team times. Your coordination agent queries coordinates, then hands the localized offset to the scheduling agent. The crew executes these tasks sequentially, ensuring that follow-up actions occur only when the target office is awake. This eliminates timezone confusion from autonomous multi-agent pipelines.

Autonomous DST Compliance

The `get_dst_status` tool gives your compliance agent the exact daylight saving state of any operational hub. Your agent cross-references this with active shifts to adjust payroll and dispatch schedules automatically. Because CrewAI agents run autonomously, the compliance agent monitors these shifts in the background. If a DST boundary is crossed, the agent logs the change and updates the shared memory.

Global Fleet Offsets

Using `list_timezones` and `get_time_by_zone` allows your logistics crew to map out global delivery routes based on current local times. The researcher agent pulls the zone list, while the router agent calculates optimal arrival windows. To maintain high availability, the moderator agent uses `check_api_status` to verify system health before starting a run. If the API is down, the moderator agent instructs the crew to use cached offsets.

Setup guide

Set up TimezoneDB MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke TimezoneDB tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="TimezoneDB Analyst",
    goal="Access and analyze TimezoneDB data via MCP.",
    backstory="Expert analyst with direct TimezoneDB access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent TimezoneDB transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="TimezoneDB Analyst",
        goal="Access and analyze TimezoneDB data via MCP.",
        backstory="Expert analyst with direct TimezoneDB access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent TimezoneDB transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by TimezoneDB. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect TimezoneDB now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about TimezoneDB MCP in CrewAI

Pass the server URL directly into your agent's configuration using the `mcps` parameter. You can restrict access so only your scheduling agent can query the timezone data.

Yes. Use `MCPServerHTTP` with a `tool_filter` to expose only specific tools to certain agents. This prevents your researcher agent from calling administration endpoints unnecessarily.

Agents share results through CrewAI's built-in short-term memory. Once the scheduling agent gets an offset, the rest of the crew uses that cached value for subsequent tasks.

The server supports stdio, SSE, and Streamable HTTP transports, allowing your crew to connect regardless of where your agents are hosted.

Vinkius manages authentication via a single endpoint token, preventing your CrewAI agents from ever seeing or exposing raw API keys. Location coordinates are processed inside a zero-trust sandbox and immediately discarded after execution.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript