MarineTraffic MCP Server
About
A Model Context Protocol server that provides access to MarineTraffic vessel tracking data, enabling AI assistants like Claude to query real-time vessel positions, details, and search vessels by name, MMSI, IMO, or type.
Details
- Author
- MCP-Mirror
- Downloads
- 330
- Categories
- Other
Jump to
- get_vessel_position: Real-time position of a vessel by MMSI or IMO
- get_vessel_details: Detailed vessel information by MMSI or IMO
- search_vessels: Search by name, MMSI, IMO, or vessel type
- get_vessels_in_area: Vessels within a specified geographic area
- vessel://{identifier} resource: Direct access to vessel data by identifier
- vessels://area/{lat}/{lon}/{radius} resource: Area-based vessel list
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MarineTraffic MCP ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install Node.js 18 or higher, obtain a MarineTraffic API key, clone the repo, run npm install and npm run build, then configure the server in your MCP settings file (e.g., claude_desktop_config.json) with the MARINETRAFFIC_API_KEY environment variable.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"marinetraffic mcp server": {
"marinetraffic": {
"command": "node",
"args": [
"/path/to/marinetraffic-server/build/index.js"
],
"env": {
"MARINETRAFFIC_API_KEY": ""
}
}
}
}
}
McpServers
{
"marinetraffic": {
"command": "node",
"args": [
"/path/to/marinetraffic-server/build/index.js"
],
"env": {
"MARINETRAFFIC_API_KEY": ""
}
}
}
MarineTraffic MCP Server
A Model Context Protocol (MCP) server that provides access to MarineTraffic vessel tracking data.
Features
This MCP server provides the following capabilities:
Tools
- get_vessel_position: Get real-time position of a vessel by MMSI or IMO number
- get_vessel_details: Get detailed information about a vessel by MMSI or IMO number
- search_vessels: Search for vessels by name, MMSI, IMO, or vessel type
- get_vessels_in_area: Get vessels in a specified geographic area
Resources
- vessel://{identifier}: Information about a vessel by MMSI or IMO number
- vessels://area/{lat}/{lon}/{radius}: List of vessels in a specified geographic area
Installation
Prerequisites
- Node.js 18 or higher
- A MarineTraffic API key (available from MarineTraffic API Services)
Setup
1. Clone this repository or download the source code
2. Install dependencies:
cd marinetraffic-server
npm install
3. Build the server:
npm run build
Configuration
The server requires a MarineTraffic API key to function. You can provide this through the environment variable MARINETRAFFIC_API_KEY.
MCP Settings Configuration
To use this server with Claude, add it to your MCP settings configuration file:
For Claude Desktop App (macOS)
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"marinetraffic": {
"command": "node",
"args": ["/path/to/marinetraffic-server/build/index.js"],
"env": {
"MARINETRAFFIC_API_KEY": "your-api-key-here"
},
"disabled": false,
"autoApprove": []
}
}
}
For Claude VSCode Extension
Edit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json:
{
"mcpServers": {
"marinetraffic": {
"command": "node",
"args": ["/path/to/marinetraffic-server/build/index.js"],
"env": {
"MARINETRAFFIC_API_KEY": "your-api-key-here"
},
"disabled": false,
"autoApprove": []
}
}
}
Usage Examples
Once the server is configured and running, you can use it with Claude to access vessel tracking data:
Get Vessel Position
<use_mcp_tool>
<server_name>marinetraffic</server_name>
<tool_name>get_vessel_position</tool_name>
<arguments>
{
"identifier": "123456789"
}
</arguments>
</use_mcp_tool>
Search for Vessels
<use_mcp_tool>
<server_name>marinetraffic</server_name>
<tool_name>search_vessels</tool_name>
<arguments>
{
"vessel_name": "MAERSK"
}
</arguments>
</use_mcp_tool>
Get Vessels in Area
<use_mcp_tool>
<server_name>marinetraffic</server_name>
<tool_name>get_vessels_in_area</tool_name>
<arguments>
{
"latitude": 37.8199,
"longitude": -122.4783,
"radius": 10
}
</arguments>
</use_mcp_tool>
Access Vessel Resource
<access_mcp_resource>
<server_name>marinetraffic</server_name>
<uri>vessel://123456789</uri>
</access_mcp_resource>
API Key Limitations
The MarineTraffic API has usage limits based on your subscription plan. Be aware of these limits when using the server to avoid exceeding your quota.
Troubleshooting
- API Key Errors: Ensure your MarineTraffic API key is valid and correctly set in the environment variables.
- Rate Limiting: If you encounter rate limiting errors, the server will automatically retry with exponential backoff, but you may need to wait before making additional requests.
_Example of detailed vessel information available through the API_
API Key Limitations
The MarineTraffic API has usage limits based on your subscription plan. Be aware of these limits when using the server to avoid exceeding your quota.
Troubleshooting
- API Key Errors: Ensure your MarineTraffic API key is valid and correctly set in the environment variables.
- Rate Limiting: If you encounter rate limiting errors, the server will automatically retry with exponential backoff, but you may need to wait before making additional requests.
- No Data Found: Some vessels may not have real-time tracking data available, especially smaller vessels or those in areas with limited AIS coverage.
License
This project is licensed under the ISC License.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



