Geoapify

What the Geoapify MCP server does

The Geoapify MCP server gives an MCP-compatible client access to four location operations. Forward geocoding turns an address, place name, or other location text into candidate coordinates and address fields. Reverse geocoding takes latitude and longitude and finds the nearest street address.

The places tool searches for points of interest near a coordinate. A category filter, such as catering.restaurant, can narrow the results. Returned information includes the place name, formatted address, categories, coordinates, and distance from the search center.

The routing tool calculates distance and travel time between two coordinates. It supports drive, walk, bicycle, and transit modes, and reports distance in meters and time in seconds.

How it works

Clients can connect to the Pipeworx pack endpoint at https://gateway.pipeworx.io/geoapify/mcp. That endpoint lists the Geoapify tools together with shared Pipeworx meta-tools. The gateway's ask_pipeworx tool can route a natural-language question across the wider Pipeworx catalog, including data sources beyond this pack. The full gateway is also available at https://gateway.pipeworx.io/mcp when an agent should work with all available packs directly.

The same operations can be called without an MCP client through the gateway's HTTP tool endpoint. For example, POST https://gateway.pipeworx.io/v1/tools/geoapify_geocode accepts a JSON body containing the text argument.

A local installation uses the @pipeworx/mcp-geoapify npm package. In standalone mode, the process communicates over standard input and output and responds to MCP initialization, tool listing, and tool calls. This mode contains only the four pack-specific tools and does not include Pipeworx meta-tools or cross-catalog routing.

Setup and configuration

For a gateway connection, add the pack URL to the MCP client's server configuration:

{
  "mcpServers": {
    "geoapify": {
      "url": "https://gateway.pipeworx.io/geoapify/mcp"
    }
  }
}

For a local stdio connection, configure the client to run:

{
  "mcpServers": {
    "geoapify": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-geoapify"]
    }
  }
}

The package can also be started directly with npx -y @pipeworx/mcp-geoapify. No environment variables are documented as required for the standalone setup.

Tools and capabilities

• geocode: Finds geographic candidates from freeform location text.
• reverse_geocode: Resolves coordinates to a nearby address.
• places: Searches categorized nearby places and points of interest.
• routing: Calculates travel distance and duration for supported modes.

The Geoapify MCP server is suitable for agents that need to turn user-supplied locations into coordinates, identify nearby services, display address details, or compare journeys between two points. Tool inputs and returned fields are specific to each operation, so agents should provide the coordinates, category, radius, mode, or text needed by the selected call.

Limitations and notes

A pack endpoint does not expose only its four listed tools: it also includes shared Pipeworx meta-tools, and the exact tool scope is reported by the connection's initialize response. The standalone package avoids those additional schemas but cannot use ask_pipeworx for broader catalog routing.

The documented routing result contains distance and time, not turn-by-turn instructions.

The project is released under the MIT license.