A side-by-side look at the Arcgis Roanoke and Vessel Traffic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Arcgis Roanoke for location services work as a local process; choose Vessel Traffic MCP for location services as a local process. You can also run both side by side in one mcpServers block.
search_datasets, query_layer, layer_info.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 53/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 6 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Arcgis Roanoke | View Vessel Traffic MCP |
search_datasetsSearch City of Roanoke GIS open geospatial datasets (parcels, zoning, public works & city services) by keyword. Returns each dataset's name, summary, record_count, owner/org, and its Feature Service `url` — pass that url to query_layer / layer_info.query_layerQuery an ArcGIS Feature Service / Map Service layer by its url (from search_datasets). SQL-like `where`, comma-separated `out_fields`, `order_by`, `limit`, `offset`. Returns attribute rows (and geometry). Use where="1=1" + out_fields="*" to sample.layer_infoGet an ArcGIS Feature/Map Service layer's schema by url: fields (name + type), geometry type, total record count, and capabilities.No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"arcgis-roanoke": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-arcgis-roanoke"
]
}
}
}
{
"mcpServers": {
"tools-mcp-vessel-traffic-mcp": {
"command": "npx",
"args": [
"-y",
"@tools-mcp/vessel-traffic-mcp"
]
}
}
}