Geo logo

Geo

Geographic MCP tools for geocoding, country data, time zones, and solar events using public APIs.

Install Geo

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "geo-2": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-geo"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 5 tools correctly (6d ago).

Overview

The geo MCP server provides geographic lookups through geocoding, reverse geocoding, country, timezone, and sunrise/sunset tools. It uses OpenStreetMap Nominatim, TimeAPI.io, the Sunrise-Sunset API, and country data services behind either a hosted MCP endpoint or a local stdio package. Use it when an agent needs to turn place names into coordinates, identify locations, add regional context, or calculate local time and daylight details.

Use cases

  • Geocode user-provided addresses into coordinates
  • Reverse-geocode GPS coordinates into postal locations
  • Retrieve country facts for regional context
  • Resolve local time from latitude and longitude
  • Check daylight and twilight times for a date

Key features

  • Forward geocoding with up to five matches
  • Reverse geocoding for address components
  • Country data by name or ISO code
  • Timezone lookup from coordinates
  • Sunrise, sunset, twilight, and day-length data
  • Hosted MCP and local stdio modes

Tools5

What Geo lets your agent do. Expand a tool for its parameters.

Verified live~456 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

What it can do

From the 5 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 5
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age199 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-geo (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads415Package downloads in the last 30 days.
Last commit27d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed5Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Geo works

What geo does

The geo MCP server exposes five geographic utilities for agents and applications. It can resolve an address or place name into as many as five candidate coordinates, turn latitude and longitude into a postal location, retrieve country facts, determine a coordinate’s timezone, and return solar event data for a date.

Results are intended for common location workflows rather than spatial analysis. The available responses cover coordinate values, display names, place types, address components, country facts, timezone details, and daylight information.

How it works

The service combines several public data sources. Forward geocoding uses OpenStreetMap Nominatim. Timezone lookups use TimeAPI.io, while sunrise and sunset calculations come from the Sunrise-Sunset API. Country queries accept either a country name or an ISO code.

The timezone operation requires latitude and longitude; it does not convert a city name directly. Solar queries also use coordinates and accept an optional date in YYYY-MM-DD format. If no date is supplied, the service uses the current day.

A hosted connection is available through the Pipeworx gateway. The gateway endpoint lists the geographic tools together with shared Pipeworx meta-tools, whose exact scope is reported during MCP initialization. The same gateway can also expose the broader catalog, while ask_pipeworx can route natural-language questions to tools across that catalog.

Setup and configuration

For a remote MCP connection, configure an MCP client with the geo endpoint:

config.json
{
  "mcpServers": {
    "geo": {
      "url": "https://gateway.pipeworx.io/geo/mcp"
    }
  }
}

The package also supports local stdio use without a Pipeworx account:

config.json
{
  "mcpServers": {
    "geo": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-geo"]
    }
  }
}

Run npx -y @pipeworx/mcp-geo directly to verify that the local process starts. HTTP callers can invoke hosted tools through the Pipeworx /v1/tools/ API, including geo_geocode.

Tools and capabilities

  • geocode: Finds up to five matching places for an address or name and returns latitude, longitude, a display label, and place type.
  • reverse_geocode: Converts coordinates into street, city, country, and postal-code information.
  • get_country: Returns a country’s capital, population, currency, languages, and bordering countries using a name or ISO code.
  • get_timezone: Returns the IANA timezone, current local time, and UTC offset for supplied coordinates.
  • get_sunrise_sunset: Returns sunrise, sunset, solar noon, civil twilight boundaries, and day length in seconds for coordinates and an optional date.

Limitations and notes

The geo MCP server does not provide a city-name shortcut for timezone requests; callers must first obtain coordinates when starting from a place name. Forward geocoding may return multiple candidates, so clients should select the appropriate result rather than assume the first match is correct.

The hosted pack endpoint includes shared gateway meta-tools in addition to the five geographic tools. The local stdio mode exposes only the geographic set. No environment variables are required by the documented setup examples, and the project is licensed under MIT.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Geo

geo is an MCP server that connects AI agents to public geographic APIs for location lookups. Its main tools geocode addresses, reverse-geocode coordinates, retrieve country information, identify timezones, and return sunrise, sunset, twilight, solar-noon, and day-length data.

Install it locally by configuring your MCP client to run `npx -y @pipeworx/mcp-geo` with stdio transport. This mode does not require a Pipeworx account. You can instead use the hosted endpoint at `https://gateway.pipeworx.io/geo/mcp`.

Yes, geo works with Cursor through the hosted MCP endpoint. Add `https://gateway.pipeworx.io/geo/mcp` as the server URL in the client configuration. The hosted pack connection also lists shared Pipeworx meta-tools.

First geocode the city to obtain latitude and longitude, then call `get_timezone` with those coordinates. The timezone tool requires latitude and longitude and does not accept city names directly.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGeo AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/geo-2?style=directory)](https://allmcps.com/mcp/geo-2)
HTML Embed
<a href="https://allmcps.com/mcp/geo-2"><img src="https://allmcps.com/api/badge/geo-2?style=directory" alt="Geo on AllMCPs" /></a>