MCP Maps MCP UI

Provides an interactive map server with geocoding and a CesiumJS globe powered by OpenStreetMap data for MCP clients.

typescript

0

GitHub Stars

typescript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "uzirthapa-mcp-maps-mcp-ui": {
      "command": "npx",
      "args": [
        "-y",
        "--silent",
        "--registry=https://registry.npmjs.org/",
        "@modelcontextprotocol/server-map",
        "--stdio"
      ]
    }
  }
}

You can run an MCP server that serves a map visualization and geocoding capabilities, enabling interactive map rendering and easy integration with MCP clients. This server demonstrates a practical combination of server-side tooling and a web-based CesiumJS globe UI fed by OpenStreetMap data, useful for embedding geospatial features into your MCP apps.

How to use

You will connect to this server from an MCP client using the provided stdio configurations. Start by running the server in your development environment, then initiate an MCP client with the corresponding command to load the map tools. Use the geocode tool to search for places and the show-map tool to render a globe focused on a specific area. You can test local development workflows to verify changes quickly.

How to install

Prerequisites you need before starting include Node.js and npm. You will also clone the repository containing the map server code, install dependencies, and run the server in stdio mode for local development.

# Install dependencies
npm install

# Build and start the server in stdio mode (local development)
npm run build && node dist/index.js --stdio

Additional notes about this server

Two MCP configurations are shown for running the server locally via stdio. The first uses npx to run the server package with stdio transport. The second demonstrates a local development workflow that builds the project and starts the server from the built artifact. No API keys are required for the included data sources; the server relies on OpenStreetMap data and CesiumJS loaded from a CDN.

Tools and endpoints

The server exposes two primary tools: geocode and show-map. These tools enable geospatial queries and viewport rendering of a 3D globe, respectively. You will pass the tool inputs through the MCP App SDK to perform a geocode search or to display a map focused on a given bounding box.

Security and data policies

The server adheres to OpenStreetMap data usage policies, including rate limiting for geocoding requests. It does not require external API keys and relies on open data sources for map rendering. Content security policy (CSP) is configured to allow fetching tiles from OSM and Cesium CDN while ensuring the UI runs in sandboxed iframes.

Known cautions and limitations

Rate limiting is applied to Nominatim requests as per usage guidelines. The CesiumJS globe calls are loaded from a CDN at runtime to minimize initial bundle size. No external API keys are necessary for these features.

Available tools

geocode

Search for places by name or address using OpenStreetMap data; returns coordinates and bounding boxes.

show-map

Render the 3D globe UI focused on a specified bounding box and label.