In the DeepSeek Harness plugin ecosystem, processing geospatial data often requires additional MCP servers or external integrations. The dsh-map-tools plugin provides a set of native tools that allow the model to directly invoke map routing capabilities and present computed results as real map cards.

Core Features

The plugin includes 7 native tools, no MCP required, and registers them directly into DSH’s ctx.tools. It supports the following scenarios:

  • Route planning: driving, bus/subway transfers, walking, and cycling routes.
  • Geolocation queries: geocoding (address to coordinates) and reverse geocoding (coordinates to address).
  • POI search: search for nearby points of interest.
  • Real map cards: planned routes are automatically drawn on real map cards (Amap base map + route polyline), appearing at the end of the response.

Installation

Before installing, ensure your environment meets the following requirements:

  • DeepSeek Harness >= 0.1.2-rc.1
  • Node >= 20

Use the following command to install:

dsh plugin --profile web add dsh-map-tools

After installation, restart dsh web to call map services in a session via the map_* tool series.

Usage Examples

After installation and configuration, the model can directly call tools to complete tasks. For example:

  • Driving route planning:
    Plan a driving route from Beijing South Station to Capital Airport T3
  • Geocoding:
    Convert “No. 478 Wensan Road, Xihu District” to coordinates
  • POI search:
    What gas stations are within 1 km of 116.397428,39.90923?

Configuration and Data Sources

The plugin supports two data sources:

  • Amap: Recommended. It has the most complete data and supports all 7 tools. You need to apply for an Amap “Web Services” type Key.
  • OSM/OSRM: A free option that does not require a Key. Driving, walking, and cycling routes can use this option, but Chinese address parsing is unreliable, and it does not support transit/POI search.

Security: The Amap Key does not appear in server-side logs or pages. Static maps are fetched by the host, which carries the Key.

Known Limitations

  • Version requirement: Requires DeepSeek Harness >= 0.1.2-rc.1.
  • Platform limitation: The route map card feature requires the web profile (dsh.client.platform: web). In TUI or headless environments, the tools still work normally, but map cards cannot be displayed.
  • Number of routes: If a request contains more than 3 routes, only the first 3 are displayed.
  • OSM Chinese support: In OSM mode, Chinese address parsing is unreliable.

Conclusion

dsh-map-tools solves the integration challenge for agents processing geographic information. By using native tools and real map cards, route planning becomes more intuitive and efficient.

GitHub Repository