Magic Lane MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGICLANE_API_KEY | Yes | Your Magic Lane API key for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| static_map_renderA | Render visual map images of routes, isochrones, round-trips, and static locations. Supports route rendering with automatic calculation, pre-calculated path overlays, area views, and location-centered maps. Returns a PNG image of the rendered map. |
| route_plannerA | Calculate optimized routes between two or more locations for car, bicycle, or pedestrian transport modes. Supports multi-stop routing with automatic waypoint resolution from place names or coordinates. Returns turn-by-turn instructions, distance, duration, and route geometry. |
| round_tripA | Generate a circular round-trip route that starts and ends at the same location. Accepts a starting point as coordinates or place name, with a range parameter for time-based (seconds) or distance-based (meters) loop extent. Returns route geometry, distance, and duration for the circular route. |
| isochrone_calculatorA | Generate isochrone polygons (areas reachable within a certain time or distance) from a given starting point. Accepts either coordinates or a place/address name. If an address is provided, this tool will internally convert it to coordinates. Useful for finding reachable areas for driving, walking, or cycling. |
| reverse_geocodeA | Convert geographic coordinates to detailed address information (reverse geocoding). Supports single-point lookup, area-based search within a radius, and address lookup along a path or route. Requires at least one of: coordinates, insideArea, or along parameters. |
| geofence_managerA | Manage geofences and perform spatial queries for asset monitoring and location-based services. Supports operations:
|
| location_searchA | Search for locations, places, and points of interest by name or address to retrieve their geographic coordinates. Supports geocoding of place names, POIs, businesses, landmarks, and addresses with optional category filtering. Returns coordinates, formatted addresses, and metadata for matching locations. |
| interactive_mapC | Display an interactive map using MagicLane vector tiles and MapLibre GL JS directly in the conversation. Supports multiple display types: location view, route visualization with stops, isochrone reachability areas, round trip routes, and search result markers. The map supports pan, zoom, and click interactions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| widget_ui |
TDQS
Scored across 8 tools
Tools generally target different aspects, but geofence_manager's interactive_map overlaps with static_map_render, and isochrone_calculator's results can be rendered by static_map_render. route_planner and round_trip both produce routes, though round_trip is a specific type. These overlaps create moderate ambiguity.
Tool names follow no consistent pattern: geofence_manager (noun_noun), isochrone_calculator (noun_noun), location_search (noun_noun), reverse_geocode (verb_noun), round_trip (adj_noun), route_planner (noun_noun), static_map_render (adj_noun_noun). Mixed conventions with no discernible verb_noun or noun_verb pattern.
8 tools is reasonable for a location services MCP server. Each tool covers a distinct domain area (geocoding, routing, geofences, etc.), and the count is not excessive or insufficient.
Covers core location operations: geocoding, reverse geocoding, routing (multi-stop, round-trip), isochrones, geofence management, and map rendering. However, lacks batch operations, elevation data, or traffic-aware routing, and the bundling of interactive map within geofence_manager is a design quirk that creates a minor gap.