Provides AI assistants with maritime data including vessel tracking, port events, geographic vessel searches, and emissions reports.
Also known as vessel-api/vesselapi-mcp
- Stars
- 1
- Tools
- 19
- Downloads, 30 days
- —
- Latest version
- 2.2.1
- Last commit
- Nov 5, 2026
- License
- MIT
What is VesselAPI MCP?
VesselAPI provides AI assistants with maritime data including vessel tracking, port events, geographic vessel searches, and emissions reports. It exposes 19 tools, such as search_vessels, get_vessel, get_vessel_position.
Summary generated from the project's README
About VesselAPI MCP server
Accessing maritime intelligence through AI assistants is possible with this server, which connects tools like Claude Desktop, Cursor, Windsurf, and Claude Code to VesselAPI data. It provides a way for developers to query real-time vessel tracking, port activity, and environmental data directly within their coding or chat environments. Users must provide a VESSELAPI_API_KEY obtained from the VesselAPI dashboard to authenticate their requests.
The server includes 19 specialized tools that allow for searching vessels by IMO or MMSI, retrieving vessel positions, and checking reported ETAs. It also offers capabilities for monitoring port events such as arrivals and departures, as well as accessing EU MRV emissions reports. For geographic analysis, the server supports finding vessels within specific bounding boxes or radii. To manage API quota usage, the system includes manual pagination through limit and nextToken parameters.
What you can do with it
- 1Track specific vessel movementsAsk your AI assistant to find the latest latitude, longitude, speed, and heading for a specific ship.
- 2Monitor port activityRequest a list of all vessel arrivals and departures at a particular port within a specific timeframe.
- 3Analyze maritime emissionsRetrieve CO2 and fuel consumption data from EU MRV emissions reports for a vessel.
- 4Perform geographic vessel searchesIdentify all ships currently located within a specific radius or bounding box area.
Written from the project's README. Every use case is checked against a quote from it.
How to install VesselAPI MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall VesselAPI MCP in Claude Code
$ claude mcp add vesselapi-mcp -- npx -y vesselapi-mcpInstall VesselAPI MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"vesselapi-mcp": {
"command": "npx",
"args": [
"-y",
"vesselapi-mcp"
]
}
}
}Install VesselAPI MCP in VS Code
.vscode/mcp.json
{
"servers": {
"vesselapi-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vesselapi-mcp"
]
}
}
}Install VesselAPI MCP in VS Code CLI
$ code --add-mcp '{"name":"vesselapi-mcp","type":"stdio","command":"npx","args":["-y","vesselapi-mcp"]}'Install VesselAPI MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"vesselapi-mcp": {
"command": "npx",
"args": [
"-y",
"vesselapi-mcp"
]
}
}
}Install VesselAPI MCP in Codex
$ codex mcp add vesselapi-mcp -- npx -y vesselapi-mcpInstall VesselAPI MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.vesselapi-mcp] command = "npx" args = ["-y", "vesselapi-mcp"]
Install VesselAPI MCP in Gemini CLI
$ gemini mcp add -s user vesselapi-mcp npx -- -y vesselapi-mcpInstall VesselAPI MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"vesselapi-mcp": {
"command": "npx",
"args": [
"-y",
"vesselapi-mcp"
]
}
}
}Needs a key before it starts
Started on 16 Nov 2026 with no keys, it stopped and asked for one, so a client sees no tools until you set the variables above.
VesselAPI MCP tools 19
Detected from the READMEsearch_vesselsget_vesselget_vessel_positionget_vessel_etaget_vessel_emissionsget_vessel_casualtiesget_vessel_positions_batchsearch_portsget_portget_port_inboundget_port_eventsget_port_events_by_vessel
Show all 19 toolsShow fewer tools
list_port_eventssearch_port_events_by_portsearch_port_events_by_vesselget_vessel_last_port_eventlist_emissionsget_vessels_in_areaget_vessels_in_radius
Configuration
VESSELAPI_API_KEY
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubVesselAPI MCP Server
An MCP (Model Context Protocol) server that exposes maritime data from the VesselAPI to AI assistants like Claude Desktop, Cursor, Windsurf, and Claude Code.
Server page: vesselapi.com/mcp-server
Prerequisites
- Sign up at dashboard.vesselapi.com
- Create an API token in your dashboard
- Use the token as
VESSELAPI_API_KEYin the configuration below
Resources: Documentation | API Explorer | Dashboard | Contact Support
Features
- 19 tools covering vessels, ports, location search, and emissions
- Vessel search, positions (single and batch), ETA, emissions, and casualties
- Port search, details, port events (arrivals/departures), and port event search across all covered ports
- Geographic vessel search (bounding box and radius)
- Manual pagination to control API quota usage
Quick Start
No installation required. Configure your AI client with npx:
{
"mcpServers": {
"vesselapi": {
"command": "npx",
"args": ["-y", "vesselapi-mcp"],
"env": {
"VESSELAPI_API_KEY": "your-api-key"
}
}
}
}
Configuration
Add the JSON above to the config file for your client:
| Client | Config file |
|---|---|
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) |
| Cursor | .cursor/mcp.json or ~/.cursor/mcp.json |
| Claude Code | claude mcp add, which writes .mcp.json in the project or ~/.claude.json for user scope |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
Tools
Vessel Tools
| Tool | Description |
|---|---|
search_vessels |
Search vessels by name, IMO, MMSI, flag, type, callsign, or year built |
get_vessel |
Get detailed vessel information |
get_vessel_position |
Get the latest stored vessel position (lat/lon, speed, heading, timestamp); it may be hours or days old |
get_vessel_eta |
Get the ETA the vessel last reported (declared, not predicted) |
get_vessel_emissions |
Get EU MRV emissions reports (CO2, fuel consumption) |
get_vessel_casualties |
Get marine casualty records |
get_vessel_positions_batch |
Get positions for multiple vessels at once (with optional time range) |
Port Tools
| Tool | Description |
|---|---|
search_ports |
Search ports by name, country, type, size, region, harbor size, or harbor use |
get_port |
Get port details by UN/LOCODE |
get_port_inbound |
Get vessels reporting a port as their destination, within an ETA window |
get_port_events |
Get arrivals/departures for a port (last 2 hours unless timeFrom is given) |
get_port_events_by_vessel |
Get port events for a vessel (last 2 hours unless timeFrom is given) |
list_port_events |
List port events across all covered ports, with filters for time, country, port, vessel, or event type |
search_port_events_by_port |
Search port events by port name |
search_port_events_by_vessel |
Search port events by vessel name |
get_vessel_last_port_event |
Get the most recent port event for a vessel |
Emissions Tools
| Tool | Description |
|---|---|
list_emissions |
List EU MRV emissions reports, with an optional reporting-year filter |
Location Tools
| Tool | Description |
|---|---|
get_vessels_in_area |
Find vessels with an AIS position in a bounding box (default last 2 hours, at most 4 hours) |
get_vessels_in_radius |
Find vessels with an AIS position within a radius of a point (default last 2 hours, at most 4 hours) |
Pagination
All list endpoints support limit and nextToken parameters for manual pagination. When more results exist, the response includes a nextToken. Pass it in the next call to get the next page.
Development
git clone https://github.com/vessel-api/vesselapi-mcp.git
cd vesselapi-mcp
npm install
npm run build
npm run build # Build the server
npm run typecheck # Type-check without emitting
npm run clean # Remove build artifacts
Testing with MCP Inspector
VESSELAPI_API_KEY=your-key npx @modelcontextprotocol/inspector node dist/index.js
Attribution
Data attribution is listed at https://vesselapi.com/disclaimer#sources.
License
MIT
VesselAPI MCP questions
How do I add VesselAPI MCP to Claude Code?
Run claude mcp add vesselapi-mcp -- npx -y vesselapi-mcp in your terminal. Add --scope user to make it available in every project.
How do I add VesselAPI MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does VesselAPI MCP provide?
It exposes 19 tools, including search_vessels, get_vessel, get_vessel_position, get_vessel_eta, get_vessel_emissions.
How do I configure the VesselAPI MCP server?
You can configure it by adding a JSON block to your AI client's configuration file using npx and providing your VESSELAPI_API_KEY.
What kind of vessel information can I retrieve?
You can search for vessels by name, IMO, or MMSI, and retrieve detailed information, positions, ETAs, emissions reports, and casualty records.
Can I search for vessels in a specific geographic area?
Yes, the server includes tools to find vessels within a bounding box or a specific radius.
How does pagination work in the API?
List endpoints use limit and nextToken parameters; when more results are available, the response includes a nextToken to fetch the next page.