MCP server for MarineTraffic vessel tracking
Marinetraffic MCP server exists for a simple reason — assistants are far more useful when they can act on Marinetraffic directly instead of describing what you should do. MCP server for MarineTraffic vessel tracking.
A Model Context Protocol (MCP) server that provides access to MarineTraffic vessel tracking data.
Once Marinetraffic is connected, these are the calls the assistant has available:
get_vessel_position — Get real-time position of a vessel by MMSI or IMO numberget_vessel_details — Get detailed information about a vessel by MMSI or IMO numbersearch_vessels — Search for vessels by name, MMSI, IMO, or vessel typeget_vessels_in_area — Get vessels in a specified geographic areaTools — The Tools tool exposed by this serverResources — The Resources tool exposed by this serverPrerequisites — The Prerequisites tool exposed by this serverSetup — 1. Clone this repository or download the source code 2. Install dependencies:You will need one environment variable: MARINETRAFFIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @smithery/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Marinetraffic's toolset — get_vessel_position, get_vessel_details, search_vessels and 5 more — is a fair guide to whether it matches your workflow. It is maintained by Cyreslab-AI; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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 |
| Tools | The Tools tool exposed by this server. |
| Resources | The Resources tool exposed by this server. |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Setup | 1. Clone this repository or download the source code 2. Install dependencies: |
{
"mcpServers": {
"marinetraffic": {
"command": "node",
"args": ["/path/to/marinetraffic-server/build/index.js"],
"env": {
"MARINETRAFFIC_API_KEY": "your-api-key-here"
},
"disabled": false,
"autoApprove": []
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MARINETRAFFIC_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.