[mattpodwysocki]

Summary

Adds the two skills the Mapbox MCP Server serves over the MCP Skills extension (SEP-2640), so this repo is the only copy of them. mapbox/mcp-server#295 bundles them from a pinned commit of this repo at build time instead of keeping its own.

• mapbox-map-display: showing tool results with render_map_tool by passing refs, several results on one map, hand-placed markers with mapbox_id, base map restyling, and when a static image is right instead.
• mapbox-reachability-analysis: places within a travel time or distance. Isochrone, then bbox_tool, then category search in that box, then points_within_polygon_tool to drop places in the box's corners, then one map with the area and only the places inside it.

Each has evals/evals.json (4 and 3 evals) and a README entry.

Fixes to existing skills

mcp-server#295 will also serve mapbox-location-grounding and mapbox-search-patterns, and it checks that every tool a skill names exists. These had a few that don't match the server:

• mapbox-location-grounding: the visual step used static_map_image_tool. It now uses render_map_tool with the results' refs, and keeps static images for when the user asks for an image file. That matches the MCP server's own instructions.
• mapbox-location-grounding: said ground_location_tool returns a static map image. It returns a mapboxRender.ref for render_map_tool.
• mapbox-search-patterns/references/optimization-combining.md: point_in_polygon_tool (doesn't exist) is now points_within_polygon_tool, and the static-map example is now render_map_tool.
• mapbox-search-patterns/references/workflows.md: bounding_box_tool is the DevKit server's; the runtime server's is bbox_tool.

Testing

• npm run check passes on a clean checkout: format, spellcheck, markdownlint, Codex plugin build and validation, and skill validation.
• The two new skills' content is what mcp-server#295 already tests: it loads them strictly through the MCP SDK's skills support and reads them back with the SDK's SkillsClient (sizes, digests, frontmatter), and MCP Inspector --verify --require-digests reports no conformance errors.

🤖 Generated with Claude Code

[mattpodwysocki]

@ctufts could you take a look at this one when you get a chance? mcp-server#295 bundles these two skills at build time, so it's waiting on this to merge before we can cut the release.

[ctufts]

Doesn't this skill have direct overlap with the location-grounding skill? Is it solving a specific problem? From grounding skill:

### Proximity search with routing context

For "find [category] within X minutes of [location]":

1. Geocode the origin if needed: `search_and_geocode_tool(address)`
2. Get the reachable area: `isochrone_tool(coordinates, profile, contours_minutes)`
3. Search for POIs: `ground_location_tool(longitude, latitude, query: "category")` — the isochrone
contours tell the user what's within each time band

Or more directly: `ground_location_tool` returns both nearby POIs and isochrone reachability in one
call, which covers most proximity + routing use cases without additional composition.

[mattpodwysocki]

Fair question. They overlap on the question but not the answer: ground_location_tool fetches nearby POIs and the isochrone in parallel and never filters one by the other (it only returns a contour summary, no polygon). So "coffee within a 10 minute walk" can include a place across a river that's close as the crow flies but 25 minutes on foot. This skill keeps only places actually inside the reachable area.

Updated the grounding skill in e111a40 so there's one owner: its "Proximity search with routing context" and "Area reachability" sections now hand "within X minutes" questions to this skill, and keep ground_location_tool for "what's near here" and neighborhood context.

[ctufts]

Should this be explicit to be used during a non-"build" use case?

[mattpodwysocki]

Yes, good call. In e111a40 the description now says it's for showing results in the conversation and not for building a page or app, and there's a "When not to use it" section: when you're building, write GL JS code (mapbox-web-integration-patterns) with a token from list_public_tokens_tool. A render_map_tool preview is still fine for checking data along the way. Same note in the README entry.