
maplibre-mcp
io.github.birkskyumPublished by GitHub account birkskyumv0.9.2Updated Oct 24, 2026
An MCP server that lets AI agents check, render and show MapLibre styles
Overview
A local MCP server that lets an AI agent validate, inspect, render and preview MapLibre styles, so it can see and fix the map it is editing.
- What you can do
- Validate styles against the MapLibre Style Specification and look up spec and GL JS API details, with suggestions for misspelled names and notes on unsupported methods. Read sources and vector tiles to list source layers, fields and sample features, and find layers that reference missing data. Diagnose why each layer does or does not draw at a place and zoom, including filters, paint and missing sprites or fonts. Render a style to PNG from a chosen camera or bounds, and compare two style versions or two renderers side by side. Give the user a live map link that follows the style file, render a whole web page with a map, and show GeoJSON maps in MCP Apps clients. List sources served by a self
- When to use it
- Use it when an agent writes or edits MapLibre styles and needs to check the result visually instead of guessing, or when a layer fails to draw and the cause must be found in the real tiles. It suits agents without a shell, in sandboxes or chat apps, that cannot build their own renderer.
- Requirements
- Local process run with npx, needing Node.js 22 or newer. Rendering with MapLibre GL JS uses an installed Google Chrome, or Chromium can be installed on first render; a container image is offered for sandboxes and CI. Optional environment variables MAPLIBRE_MCP_TOOLSETS and MARTIN_URL; the Martin toolset needs a Martin server, and Native rendering needs an extra package. No API key.
Installation
In SourceWeft
- Open maplibre-mcp in the dashboard and add it to a workspace.
- 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
maplibre-mcp
[birkskyum/maplibre-mcp MCP server]
An MCP server that lets an AI agent see the MapLibre map it works on, check it, and show it to you.
[A hiking map of the Alps in 3D, with the Matterhorn against an evening sky]
A hiking style an agent made from one prompt, rendered with render_style from a camera placed above Zermatt.
A coding agent can write a MapLibre style, but it can't see the map. So it hands you untested work, or first spends minutes building a renderer of its own, and it reaches for what it remembers, like an older MapLibre GL JS or Mapbox. With maplibre-mcp the agent renders the style, looks at the image and fixes what it sees, and you get a link to a live map that redraws as it edits the file. It runs on your machine and needs no API key.
Two things it is good for:
- Editing a style by chat while you watch the map change. "Make the water darker", "thin the footpaths in the village". The agent edits the file and checks the render, and your open map follows.
- Finding out why a layer doesn't draw. The agent reads the real tiles, sees which layers draw at a place and why the others don't, and fixes the filter.
An agent with no shell to build its own tools, in a sandbox or a chat app, gets the most from it.
Website · Getting started · Examples · Tools
Install
It needs Node.js 22 or newer.
Claude Desktop, Cursor, Windsurf and most other clients read this JSON. Getting started says where each one keeps it.
Rendering with MapLibre GL JS uses the installed Google Chrome. Without Chrome, the first render fails with the command that installs the Chromium it can use instead.
In a sandbox or in CI, where no browser can be installed, use the container image ghcr.io/birkskyum/maplibre-mcp, which has the server and its Chromium. Containers and sandboxes shows how.
Command line
Agents that work in a shell, and people, can also run the rendering and data tools, and the GL JS API lookup, as commands, without setting up MCP. A style is a file or a URL.
The images go to map.png, compare.png and renderers.png, or to --out. npx -y maplibre-mcp --help lists the options, and Command line has the details. To validate, format or migrate a style, use gl-style-validate, gl-style-format and gl-style-migrate from @maplibre/maplibre-gl-style-spec.
Tools
validate_stylechecks a style against the MapLibre Style Specification, and lists each problem with the path to its property.describe_style_speclooks up a layer type, property, source type or expression, with its documentation and the GL JS and Native versions that support it. For a misspelled name, it suggests the closest real ones.describe_gl_js_apilooks up a class, method, option or event of MapLibre GL JS, with its signature, documentation, default and examples, in the type definitions of the version the server renders with, or of another version. It also says when a method is not in MapLibre, like one from Mapbox GL JS.describe_sourcesreads the TileJSON, PMTiles header or GeoJSON of each source in a style, lists the source layers and fields, and finds layers that use a source layer or field that is not there.inspect_tilereads the vector tile at a place and lists each source layer with its geometry types, the values of its fields and how often they occur, and a few example features, plus the zoom range of the source and the source layers the tile lacks. The source can be a source in a style, a TileJSON URL like a Martin source, a PMTiles archive or a tile URL, with MVT or MLT tiles.debug_layerssays for each layer of a style whether it draws at a place and zoom, and if not, why, like a missing source layer, a filter that matches nothing (next to the values the data has), a fill layer without polygons, paint that comes out as 0 or transparent, or icons missing from the sprite. It also notes text that falls back to local fonts, since the glyph server lacks its font stack.render_stylerenders a style to a PNG, and reports map errors, missing fonts and missing icons. It takes a center, zoom, bearing and pitch, bounds to fit, or a camera position and a point to look at over 3D terrain.preview_stylegives the user a link to a live, interactive map of a style. The map follows the style file as it changes, and an agent with no files to write sends a changed style to the same link.render_pagerenders a web page with a map, for what a style cannot hold, like plugins, controls and the page's code. It reports the page's errors and failed requests, and can run a script in the page first.compare_stylesrenders two versions of a style at the same camera, and returns one image with the style before, after, and their differences in red.compare_renderersdoes the same for one style in two renderers, for example to check that a style looks the same on the web and on mobile.show_mapshows the user an interactive map with GeoJSON layers and markers on an OpenFreeMap basemap, in clients that support MCP Apps.martin_list_sourceslists the tiles, sprites, fonts and styles a Martin server serves, with the URLs to use in a style.search_ecosystemsearches Make with MapLibre for SDKs, plugins, routing, geocoding, styling and tiling libraries, hosted APIs, products and consultancies, filtered by kind and platform, with their links and live demos.find_basemapslists the basemaps in Make with MapLibre with their style URLs or tile sources, whether they need an API key, and the attribution or logo their provider requires on the map.
The data of Make with MapLibre is © Birk Skyum, under CC BY 4.0, and both tools end with its credit.
The tools that take a style accept it as an object (style), a URL (url) or a file (path, relative to where the server runs). The tool reference lists every parameter.
Toolsets
The tools are grouped by the MapLibre project they belong to. style, gl-js and ecosystem are on by default. Choose others with --toolsets, or with the MAPLIBRE_MCP_TOOLSETS environment variable, and all turns on every toolset:
With any renderer on, there are render_style and compare_styles, and with two or more, compare_renderers. Rendering with MapLibre Native needs one more package, and rendering with Martin needs a Martin build with rendering. Rendering covers both.
Remote server
--http serves Streamable HTTP at http://127.0.0.1:3100/mcp instead of stdio, and --host and --port change the address. On a loopback address it only answers requests from localhost. On any other address it does not read or write files, it still fetches the URLs it is given from its own network, and it has no authentication, so put it behind a proxy that has. Remote server has the details.
Development
License
MIT © 2026 Birk Skyum
Source: README.md at commit af12637
Tools
0Version history
7- v0.9.2LatestOct 5, 2026
- v0.9.1Oct 5, 2026
- v0.8.1Oct 3, 2026
- v0.8.0Oct 3, 2026
- v0.7.1Sep 30, 2026
- v0.7.0Sep 30, 2026
- v0.6.1Sep 27, 2026
Score
50% 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
- License10 pts