How to Use the Datalastic Maritime MCP in CrewAI

Q: Can a CrewAI analyst agent use Datalastic Maritime to map historical routes?

Yes, the analyst agent calls getvesselhistory to retrieve past coordinates. It then passes those coordinates to a writing agent to compile a route summary.

Q: How do CrewAI agents handle errors when a Datalastic Maritime vessel search fails?

If searchmaritimevessels returns no results, the searching agent uses its internal memory to try alternative spelling variations or asks a sister agent to search by port instead using searchportsbyname.

Q: Is it possible to limit which Datalastic Maritime tools a specific CrewAI agent can use?

Yes, you use the toolfilter option in CrewAI's MCP configuration. This prevents a research agent from executing heavy queries like getvesselhistory while leaving basic searches open.

Deploy a cooperative team of specialized agents to monitor global shipping lanes and analyze vessel history with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Datalastic Maritime MCP to CrewAI

Create your Vinkius account to connect Datalastic Maritime to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Datalastic Maritime with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent Maritime Operations with CrewAI

Monitoring a global supply chain requires different perspectives. With CrewAI, you assign one agent to search for ships using `search_maritime_vessels` while a second agent verifies destinations. This MCP Server configuration lets them share tools directly. These agents share a common memory space, passing vessel details back and forth. The search agent finds the ship, and the logistics agent instantly queries its destination port using `get_port_details` without manual handoffs.

Autonomous Port Monitoring and Local Search

Instead of waiting for manual queries, your crew actively monitors specific coastlines. The MCP tools let an agent use `search_ports_by_country` to list active docks and then scan the surrounding waters. By calling `find_vessels_in_radius` around those coordinates, the agent identifies incoming traffic. This builds a real-time log of arriving cargo ships without human intervention.

CrewAI Multi-Agent Vessel History Audits

Auditing a ship's performance requires combining historical routes with physical specifications. A research agent uses `get_vessel_pro_specs` to find cargo limits, while an analyst agent pulls `get_vessel_history` to check route efficiency. The coordinator agent then compares the actual track with the ship's design capacity. This multi-agent MCP pipeline turns raw AIS data into structured reports.

Setup guide

Set up Datalastic Maritime 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 Datalastic Maritime tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Datalastic Maritime 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="Datalastic Maritime Analyst",
        goal="Access and analyze Datalastic Maritime data via MCP.",
        backstory="Expert analyst with direct Datalastic Maritime access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Datalastic Maritime 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 Datalastic. 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 Datalastic Maritime 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 Datalastic Maritime MCP in CrewAI

You pass the MCP Server URL to the agents in your crew configuration. This gives both your tracking agent and your logistics agent access to tools like `get_vessel_status` and `get_port_details`.

Yes, the analyst agent calls `get_vessel_history` to retrieve past coordinates. It then passes those coordinates to a writing agent to compile a route summary.

If `search_maritime_vessels` returns no results, the searching agent uses its internal memory to try alternative spelling variations or asks a sister agent to search by port instead using `search_ports_by_name`.

Yes, you use the `tool_filter` option in CrewAI's MCP configuration. This prevents a research agent from executing heavy queries like `get_vessel_history` while leaving basic searches open.

All queries to trace vessel positions or inspect port details run through a zero-trust, ephemeral V8 sandbox on Vinkius. Your tracking parameters are never logged or used to train public models.

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