An astronaut overseeing a futuristic data hub

Connect Pelias Geocoder to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn raw coordinates and addresses into structured map data.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Pelias Geocoder.

  1. 01

    Search country filter

    Filters search results to specific countries using ISO 3166 limits. It helps your agent drop irrelevant international results.

  2. 02

    Reverse distance limit

    Sets a specific search radius around a coordinate. Use this to restrict reverse geocoding to a tight circle.

  3. 03

    Reverse geocode

    Converts latitude and longitude into human-readable addresses. It extracts properties used for mapping pins.

  4. 04

    Search autocomplete

    Provides real-time suggestions as you type. It's useful for building predictive text or finding POIs quickly.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Pelias Geocoder.

  1. 05

    Search layer filter

    Filters queries by specific GIS datasets. This lets your agent target specific layers of geographic information.

  2. 06

    Structured geocoding

    Performs precise lookups by isolating specific address components like region or street. It targets specific location limits.

  3. 07

    Lookup place ID

    Retrieves detailed schema properties for a specific place ID. It pulls rich metadata for a known location.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Pelias Geocoder.

  1. 08

    Search bounding box

    Finds all geometries within a specific rectangular area. It validates what falls inside your defined map coordinates.

  2. 09

    Search focus bias

    Tells the engine to prioritize results near a specific GPS point. This keeps your agent's search focused on a local area.

  3. 10

    Search geocode

    The standard capability for turning addresses into geographic locations within the Pelias ecosystem.

Real work

What teams actually run

01

Batch Address Cleaning

Convert a list of messy address strings into clean, structured coordinate data.

02

Local Search Optimization

Force your agent to prioritize results near a specific user location using focus bias.

03

Geofencing Tasks

Identify all points of interest that fall within a specific rectangular bounding box.

04

POI Data Enrichment

Use place IDs to pull deep metadata for specific locations in your database.

Automate a task

Put Pelias Geocoder to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Pelias Geocoder works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Pelias Geocoder to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

993ms average. Fast in production.

Pelias Geocoder is checked daily against the live service.

Daily averagePeak 1256ms
Oct 3Today
Fastest day
814ms
Slowest day
1256ms
14-day trend
Slowing+32%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Pelias Geocoder, so you can see the experience inside your AI.

It does not authenticate your account with Pelias Geocoder. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Pelias Geocoder Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_9xauhtmLx4FJnpssXKIJfawJuO9h0Fd6rFMjRoZ7/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Pelias Geocoder capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "pelias-geocoder-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_9xauhtmLx4FJnpssXKIJfawJuO9h0Fd6rFMjRoZ7/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Pelias Geocoder in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Pelias Geocoder owners hand off.

This MCP is built for professionals working with spatial data and geographic information systems.

  • 01

    Map Engineers

    They use the MCP to extract and resolve spatial boundaries and JSON arrays.

  • 02

    Data Operations

    They use it to map lists of coordinates to human-readable addresses.

  • 03

    City Planners

    They use it to evaluate points of interest and structural boundaries.

FAQ

Questions Pelias Geocoder owners ask.

  • 01

    Which AI clients can use this MCP?

    You can use this MCP with any compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 02

    Do I need to host the Pelias engine myself?

    No. Vinkius hosts the MCP for you, so you only need to provide your Pelias API credentials.

  • 03

    Can I limit my searches to a specific country?

    Yes. You can use the search_country_filter capability to restrict results to specific ISO 3166 boundaries.

  • 04

    How does the MCP handle reverse geocoding?

    It uses the reverse_geocode capability to turn coordinates into addresses, and you can use reverse_distance_limit to control the search radius.

  • 05

    Is it possible to search within a specific area?

    Yes. You can use the search_bounding_box capability to find items within a specific rectangular coordinate range.

  • 06

    Can I use Pelias bounds configuring explicit extraction of local custom data stores?

    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.

  • 07

    How explicitly strict are the parameter bounds when I invoke bounded reversed logistics natively?

    You map explicit limits using standard decimal notation gracefully parsing constraints natively: lat=40.73 and lon=-73.93. The limits parse efficiently checking the closest explicit street JSON outputs securely returning structured bounded nodes.

  • 08

    Is the structured Autocomplete log bound explicitly evaluating live typing constraints?

    Absolutely structurally globally bound. Command the search_autocomplete natively with partial strings (e.g., '100 Main S'), and the AI extracts arrays modeling how your specific UI limit bounds react dynamically effortlessly.

Connect Pelias Geocoder to Claude, Cursor, ChatGPT & more