Mapsi Mcp

io.github.algolayertechnologiesPublished by GitHub account algolayertechnologiesv1.0.0Updated Oct 24, 2026

Geocoding, routing, isochrone, H3, elevation and 13 more geospatial tools via OpenStreetMap.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Local MCP server that gives an assistant geospatial tools — geocoding, routing, isochrones, H3, elevation and more — built on OpenStreetMap data via the Mapsi…

What you can do
  • Geocode places and look up locations
  • Compute routes and travel isochrones
  • Work with H3 hexagon indexing
  • Retrieve elevation data
  • Access roughly 18 geospatial tools in total, per the provider's description
When to use it
Useful when an assistant needs to resolve addresses or place names, plan routes, measure travel reach, or do other map and location analysis inside a chat session, without leaving the desktop client.
Requirements
Runs as a local stdio process, installed from the npm package mapsi-mcp, so Node.js and a desktop MCP client are needed. A Mapsi API key must be supplied in the MAPSI_API_KEY environment variable; the key is obtained from the provider's site. Network access is required for the underlying geospatial service.
Before you install
The server requires an API key stored in MAPSI_API_KEY, which is sent to the Mapsi service; check the provider's quota, pricing and data-handling terms before use. Queries and coordinates you submit leave your machine to that third-party service. No tool list or documentation was supplied, so review the actual tools before relying on them.

Installation

In SourceWeft

  1. Open Mapsi Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.