A side-by-side look at the MCP Server and Open Waters AIS MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server for location services work as a local process; choose Open Waters AIS for location services over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Server when
You need dedicated capabilities in the Location Services domain.
uriThe resource URI to read (e.g., `mapbox://categories`, `mapbox://categories/ja`)
Open Waters AIS tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Server is categorized under Location Services and uses a local stdio subprocess. Open Waters AIS belongs to Location Services and uses a remote HTTP/SSE transport. Pick MCP Server for location services work and Open Waters AIS for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Server has no declared pricing — check the project's own site. Open Waters AIS has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-server-139 and open-waters-ais as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server has a quality signal of 63/100 (Good) with 0 views, 0 installs and 361 GitHub stars. Open Waters AIS has 43/100 (Fair) with 0 views, 0 installs and 7 GitHub stars.