Pelias Geocoder

Pelias Geocoder MCP Connector for Claude

A+

Map geospatial structures via Pelias APIs — convert coordinates, perform reverse geocoding, autocomplete POIs, and retrieve addresses natively by AI logs.

10 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Empower your logical AI generative environments extracting robust structural limits across the Pelias Geocoding Platform. Execute formal explicitly bounded parameter checks natively identifying coordinates logically structuring text into GPS metrics via Search/Autocomplete arrays implicitly evaluating point-of-interests securely mapped seamlessly.

What you can do

  • Geocoding Pipelines — Execute logical bounded structures checking human-readable address parameters seamlessly natively resolving to structured bounding coordinates dynamically
  • Reverse Geocoding — Dispatch explicit strict positional bounds (Lat/Long) parsing logic pulling real-world place arrays locally checking limits internally gracefully
  • Structural Autocompletion — Query dynamic bounding nodes checking continuous input logs mapping explicit native POIs parsing geographic records securely
  • Place Queries — Map formal instances determining the exact JSON limits corresponding to specific GID properties returned seamlessly

How it works

  1. Authorize natively linking your own hosted/cloud structure parameters implicitly
  2. Configure explicit Pelias bounds entering base URLs structurally and logging your valid API Token dynamically
  3. Execute spatial limits checking text and coordinates seamlessly querying instances via chat

Who is this for?

  • Map Engineers — check JSON spatial array limits directly extracting and resolving boundaries internally resolving missing bounds elegantly
  • Data Operations — log strict explicit matrices mapping lists of coordinates into human addresses checking batch results effortlessly natively
  • City Planners — evaluate internal POIs extracting structural boundaries encapsulating geospatial points seamlessly structurally returning explicit configurations
geocodingreverse-geocodingpoi-searchautocompletemap-dataspatial-analysis

10 tools expose this connector's capabilities to your AI agent.

search_autocomplete

Retrieve explicit Cloud logging tracing explicit Keypress constraints

lookup_place_id

Irreversibly vaporize explicit validations extracting rich schema properties

reverse_geocode

Perform structural extraction of properties driving active OSM Pins

reverse_distance_limit

circle.radius` checking exactly how far from the point Pelias should search. Retrieve the exact structural matching verifying Reverse alternatives

search_geocode

Identify bounded routing spaces inside the Headless Pelias Maps

search_bounding_box

rect` figuring out what geometries strictly fall inside the map coordinate rectangle. Dispatch an automated validation check routing explicit Box arrays

search_country_filter

country` fetching localized boundaries matching ISO 3166 limits. Identify explicit tracking networks dropping extraneous international domains

search_focus_bias

point` enforcing Pelias to prioritize results physically closer to the GPS trace. Inspect deep internal arrays mitigating specific Center biases

search_layer_filter

Enumerate explicitly attached structured rules exporting active GIS datasets

structured_geocoding

g address=X region=Y safely isolating terms. Identify precise active arrays spanning native Location limits

See how to talk to your AI agent using Pelias Geocoder.

Log natively bounding coordinates logically extracted seamlessly for the explicit address '10 Downing St, London'.

Queried structured native limits logically hitting endpoints globally. Extracted JSON gracefully identifying explicit bounds: Latitude `51.503`, Longitude `-0.127`. Internal array mappings confirmed natively flawlessly active.

Reverse query the explicit structure gracefully checking logical metadata coordinates lat `40.7484` and lon `-73.9856` natively limits.

Mapped explicit target bounds successfully over Reverse logical APIs natively. The array extracted precisely identifies structural limits as exactly 'Empire State Building, New York'. Would you like the full logical JSON bounds?

Check suggestions validating autocompletion logs evaluating string inputs structurally starting with bounds 'Statue of L'.

Processed parameter logically extracting lists mapped explicitly in 'autocomplete' natively limits safely. First bound gracefully resolving is structurally 'Statue of Liberty, NY' explicitly internally validating bounds gracefully directly.

Yes. This configuration inherently parses dynamic host architecture. You explicitly bind the native Base URL to point strictly toward your configured self-hosted arrays or Pelias-compatible public limit providers natively globally.

Related Connectors