gfw-mcp-js

To generate Global Fishing Watch map screenshots, you query vessel, event, or area data using the MCP tools and render the map visuals using the scripts/screenshot_gfw.js script. This automated approach captures vessel tracks, fishing events, and port visits as image files.

Yes, you can calculate area-based fishing activity hours for MPAs, EEZs, and RFMO regions. The Skill queries Global Fishing Watch data for these specific areas and generates corresponding map screenshots to visualize the regional activity.

Yes, a Global Fishing Watch API token is required for all actions. You must provide this token to authenticate MCP tool requests when searching for vessels, retrieving fishing and port visit events, or generating area reports.

The best way to visualize vessel tracks and fishing events automatically is by using an MCP-driven script to query Global Fishing Watch data and capture map screenshots. This bypasses manual navigation by directly rendering the queried data into visual map outputs.

Yes, the automated screenshot generation works with Playwright, which is listed as a dependency. It uses Playwright to control the browser and capture the Global Fishing Watch map visuals for the queried vessels, events, or areas.

Your Global Fishing Watch map screenshot script may fail if the GFW API token is missing or invalid. All MCP tool actions strictly require proper authentication to query vessel, event, and area data before rendering the visual output.