geo_point_in_polygon — MapMap MCP Tool
geo_point_in_polygon
(geo point in polygon) is one of 47 tools on the
MapMap
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call geo_point_in_polygon from your client
- Claude Code MapMap geo_point_in_polygon run in your project directory
- Claude Desktop MapMap geo_point_in_polygon ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MapMap geo_point_in_polygon ~/.cursor/mcp.json
- VS Code MapMap geo_point_in_polygon .vscode/mcp.json
- Zed MapMap geo_point_in_polygon ~/.config/zed/settings.json
- Windsurf MapMap geo_point_in_polygon ~/.codeium/windsurf/mcp_config.json
- Cline MapMap geo_point_in_polygon ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MapMap geo_point_in_polygon ~/.gemini/settings.json
- Grok MapMap geo_point_in_polygon .mcp.json (in your project root)
- ChatGPT MapMap geo_point_in_polygon Settings → Connectors → Advanced → Developer mode
- Claude.ai MapMap geo_point_in_polygon Settings → Connectors → Add custom connector
- LangChain MapMap geo_point_in_polygon pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mapmap https://mcp.mapmap.ai/mcp
Other tools on this server
- cheapest_charging_along_route
- cheapest_fuel_along_route
- check_adr_tunnel
- check_clearance_on_route
- check_style_contrast
- cluster
- create_style
- elevation
- geo_area
- geo_bbox
- geo_bearing
- geo_centroid
- geo_destination
- geo_distance
- geo_length
- geo_nearest_point_on_line
- geo_simplify
- geocode
- get_job
- get_style
- get_usage
- heritage_narration
- list_place_categories
- list_style_layers
- match_trace
- matrix
- nearby_places
- optimise_routes
- order_stops
- places_in_view
- plan_day
- plan_errands
- plan_ev_route
- reachable_area
- replan_routes
- report_map_issue
- reverse_geocode
- route
- route_observations
- search_along_route
- set_layer_paint
- set_palette
- submit_integration_retro
- submit_optimise_job
- validate_geodata
- verify_places
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.