Geocoding MCP Server

Created By
geocoding-aia year ago
MCP server to access free geocoding
Overview

what is Geocoding MCP Server?

The Geocoding MCP Server is a Model Context Protocol (MCP) server that provides geocoding services by integrating with the Nominatim API, allowing users to convert addresses into geographic coordinates and vice versa.

how to use Geocoding MCP Server?

To use the Geocoding MCP Server, you need to install it via Node.js and configure it in your MCP client, such as Claude Desktop, by adding the appropriate command to your configuration file.

key features of Geocoding MCP Server?

  • Integration with the Nominatim API for accurate geocoding.
  • Easy installation and configuration for various MCP clients.
  • Supports Node.js environment for seamless operation.

use cases of Geocoding MCP Server?

  1. Converting user addresses into latitude and longitude for mapping applications.
  2. Reverse geocoding to find addresses from geographic coordinates.
  3. Enhancing location-based services in mobile and web applications.

FAQ from Geocoding MCP Server?

  • What is the primary function of the Geocoding MCP Server?

It provides geocoding services by converting addresses to coordinates and vice versa using the Nominatim API.

  • Is there a specific Node.js version required?

Yes, Node.js version 18.0.0 or higher is required to run the server.

  • Can I use this server with other MCP clients?

Yes, it can be configured to work with various MCP clients that support the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
geocoding-ai
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago