Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

maplibre-mcp

NPM · MAPLIBRE-MCP

An MCP server that lets AI agents check, render and show MapLibre styles

Available components

0 this week 88 Trust /100

Last scanned (13 hours ago)

Scores higher than 82% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 13 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to birkskyum/maplibre-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 46 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability37
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3229 tokens (~230/item across 14 items; 13 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
  • Structured output schemas are declared (8% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (17)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −3
    • Provenance: pass → unverified ▼ security
    • Stability: fail → pass ▲ security
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 82 to 85.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 75 to 78.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/maplibre-mcp@0.9.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo birkskyum/maplibre-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/birkskyum/maplibre-mcp/.github/workflows/publish.yml@refs/tags/v0.9.2
Rekor log index 3091670726
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:1df79ca0928e8186e1d09fe1cacdb547402d584a34942cfd98024ebf346aeab75c14259e386f76d71a8ab2091e9f9ab9b92edee145e4d1fa4d42e5e3d

Background: How many MCP packages publish verified provenance →

Dependencies 46 packages
Packages resolved 46
Stale 12
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~2,800 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_styles ~226

Renders two versions of a MapLibre style at the same camera, and returns one image with the style before, the style after, and their differences in red. Use it after changing a style, to check that the change did what you meant and nothing else, at a few places and zoom levels. Pass each style as an object, a URL or a file path.

NameTypeReqDescription
afterobjectyesThe style after the change.
bearingnumber–The compass direction at the top of the map, in degrees.
beforeobjectyesThe style before the change.
boundsarray–[west, south, east, north] to fit the map to, instead of center and zoom.
centerarray–[longitude, latitude] of the map center.
heightinteger––
pitchnumber–Tilt in degrees from looking straight down.
rendererstring–The MapLibre renderer to draw both with.
widthinteger–Width of each of the three images.
zoomnumber––

No output schema declared.

No examples provided.

debug_layers ~269

Says for each layer of a style whether it draws anything at a place and zoom, and when it draws nothing, why: it is hidden or outside its zoom range, the tile lacks its source layer, its filter matches no feature (listed with the values the tile has), a fill layer gets no polygons, its opacity, width or size is 0 or its color transparent, or icons are missing from the sprite. It also notes text that GL JS draws with local fonts and MapLibre Native leaves out, because the style has no glyphs URL or the glyph server lacks its font stack. It reads the vector tiles and GeoJSON data at the place. Use it when a layer draws nothing. Pass the style as an object, a URL or a file path.

NameTypeReqDescription
centerarray–[longitude, latitude] of the place. Defaults to the center of the style.
layersarray–Only check these layers, by id. Defaults to every layer.
pathstring–Path to a style JSON file, relative to the directory the server runs in.
styleobject–The style as a JSON object.
urlstring–URL of a style JSON document.
zoomnumber–Zoom level. Defaults to the zoom of the style.

No output schema declared.

No examples provided.

describe_gl_js_api ~212

Looks up a class, method, option, event or function of MapLibre GL JS, like "Map", "Map#flyTo", "MapOptions.maxPitch", "click" or "addProtocol", in the type definitions that GL JS ships. Returns its signature, documentation, parameters, default and examples, and for a class or an options type, its members. Answers for the GL JS version this server renders with, or for another version, like the one a project uses. Check here before using a method or option you are not sure exists in MapLibre, since Mapbox GL JS has some that MapLibre GL JS does not.

NameTypeReqDescription
namestringyesThe name to look up, like "Map#flyTo", "flyTo" or "MapOptions".
versionstring–A GL JS version or range, like "5.6.0" or "5", whose type definitions are fetched from jsDelivr. Defaults to the version this server renders with.

No output schema declared.

No examples provided.

describe_sources ~153

Reads the metadata of every source in a MapLibre style (TileJSON, PMTiles headers and GeoJSON data) and lists the source layers and fields each one provides. Then checks that every layer uses a source, source layer and fields that exist. Use it before writing layers against data you do not know. inspect_tile shows the values the fields take, and debug_layers says what each layer draws at a place. Pass the style as an object, a URL or a file path.

NameTypeReqDescription
pathstring–Path to a style JSON file, relative to the directory the server runs in.
styleobject–The style as a JSON object.
urlstring–URL of a style JSON document.

No output schema declared.

No examples provided.

describe_style_spec ~132

Looks up a name in the MapLibre Style Specification: a layer type (like "fill"), a layer or root property (like "fill-extrusion-height" or "sky"), a source type (like "geojson") or an expression operator (like "interpolate"). Returns its documentation, type, default, allowed values, expression support and which MapLibre GL JS and MapLibre Native versions support it. Check here before using a property you are not sure exists in MapLibre, since Mapbox GL JS has properties that MapLibre does not.

NameTypeReqDescription
namestringyesThe name to look up.

No output schema declared.

No examples provided.

find_basemaps ~159

Lists the basemaps in Make with MapLibre (makewithmaplibre.com): ready-made MapLibre styles from OpenFreeMap, Protomaps, MapTiler, Stadia Maps, VersaTiles and others, with their style URLs and whether they need an API key, plus raster and elevation tiles. Pass a style URL as url to render_style or compare_styles to see it, or start a style from it.

NameTypeReqDescription
freeboolean–true for only the basemaps that need no API key, false for only those that do.
querystring–Words that each basemap has to contain, in its name, provider or description, like "dark", "satellite" or "openfreemap".

No output schema declared.

No examples provided.

inspect_tile ~321

Reads the vector tile of a source at a place and zoom, and lists each source layer with its number of features, their geometry types, the values of each field and a few example features. It also gives the zoom range of the source and the source layers its metadata lists that the tile lacks. Use it to learn the values data really has, like the classes of roads, before writing filters and expressions. The source is either the id of a source in the style you pass, or the URL of a vector source: a TileJSON URL like a Martin source, a PMTiles archive, or a tile URL with {z}, {x} and {y}. Reads MVT and MLT tiles.

NameTypeReqDescription
centerarray–[longitude, latitude] of the place to read. Defaults to the center of the style or the source.
examplesinteger–How many example features to show for each source layer. Defaults to 3.
layerstring–Only list this source layer.
pathstring–Path to a style JSON file, relative to the directory the server runs in.
sourcestring–The id of a source in the style, or the URL of a vector source. Defaults to the only vector source of the style.
styleobject–The style as a JSON object.
urlstring–URL of a style JSON document.
zoomnumber–Zoom level of the tile. Defaults to the zoom of the style, or the highest zoom of the source.

No output schema declared.

No examples provided.

preview_style ~193

Gives the user a link to an interactive map of a style, served by this server on their machine, so there is no viewer page to write, no web server to start and no browser to open for them. Given a file, the map follows it and redraws when the file changes. Given the style as an object, the map shows a changed style when you pass it together with the link, as link. Pass the style as an object, a URL or a file path.

NameTypeReqDescription
linkstring–A link that this tool gave before for a style passed as an object. The map there then shows this style, and a page that has it open redraws.
pathstring–Path to a style JSON file, relative to the directory the server runs in.
styleobject–The style as a JSON object.
urlstring–URL of a style JSON document.

No output schema declared.

No examples provided.

render_page ~248

Loads a web page with a MapLibre map in a headless browser and returns a screenshot of it, so you can see a map together with the plugins, controls and code of its page, which render_style leaves out since a style cannot hold them. Also reports the errors and warnings of the page, the requests that failed and the camera of the map. Pass an HTML file, which is served together with the files in its folder, or the URL of a page. A page that keeps its map in window.map is drawn once that map has loaded everything, and script can then use the map, for example to move the camera before the screenshot.

NameTypeReqDescription
heightinteger––
pathstring–Path to an HTML file, relative to the directory the server runs in. The page can load the files next to it.
scriptstring–JavaScript to run in the page before the screenshot, like map.jumpTo({center: [7.66, 45.98], zoom: 12}). What it evaluates to is returned.
urlstring–URL of a page, for example on a development server.
widthinteger––

No output schema declared.

No examples provided.

render_style ~362

Renders a MapLibre style to a PNG image, so you can see what the style looks like, for example after changing it. Also reports what the renderer noticed, such as style errors, failed requests, and fonts and icons that are missing. Pass the style as an object, a URL or a file path. Without center, zoom or bounds, the camera stored in the style is used. For a view over 3D terrain, cameraPosition and lookAt place the camera in space, and the result gives the center, zoom, bearing and pitch of that view to store in the style.

NameTypeReqDescription
bearingnumber–The compass direction at the top of the map, in degrees.
boundsarray–[west, south, east, north] to fit the map to, instead of center and zoom.
cameraPositionarray–[longitude, latitude, altitude in metres] of the camera, to place it in space instead of with center, zoom, bearing and pitch. Needs lookAt.
centerarray–[longitude, latitude] of the map center.
heightinteger––
lookAtarray–[longitude, latitude] of the point on the ground that the camera at cameraPosition looks at, like a summit or a village.
pathstring–Path to a style JSON file, relative to the directory the server runs in.
pitchnumber–Tilt in degrees from looking straight down.
rendererstring–The MapLibre renderer to draw with.
styleobject–The style as a JSON object.
urlstring–URL of a style JSON document.
widthinteger––
zoomnumber––

No output schema declared.

No examples provided.

search_ecosystem ~278

Searches Make with MapLibre (makewithmaplibre.com), a curated directory of what works with MapLibre: SDKs and framework bindings, GL JS plugins, routing and navigation, geocoding, styling and tiling tools, AI tools (MCP servers and agent skills), hosted APIs, the products built with MapLibre, and consultancies. Use it to pick an SDK for a platform or framework, find a plugin or a service, find a platform or data source to build on, or see which products use a library. Each result has its links and a page with more. Follow up with find_basemaps for style URLs to render.

NameTypeReqDescription
kindstring–Only entries of this kind. ai is MCP servers and agent skills for MapLibre. plugin includes the routing and geocoding controls for MapLibre GL JS. routing, geocoding, styling and tiling include the h…
limitinteger–The most results to return.
platformstring–Only entries that run on this platform. Hosted services and consultancies have no platform and are kept.
querystring–Words that each result has to contain, like "react", "draw" or "routing". Leave it out to list the most prominent entries.

No output schema declared.

No examples provided.

show_map ~143

Shows the user an interactive MapLibre map in the chat, with GeoJSON layers and markers on an OpenFreeMap basemap. The user sees the map and you do not; to look at a map yourself, use render_style. Without center and zoom, the map fits the layers and markers. Needs a client that supports MCP Apps.

NameTypeReqDescription
basemapstring–The OpenFreeMap style to draw on.
bearingnumber––
centerarray–[longitude, latitude] of the map center.
layersarray––
markersarray––
pitchnumber––
zoomnumber––

No output schema declared.

No examples provided.

validate_style ~104

Checks a MapLibre style against the MapLibre Style Specification and lists every problem, each with the path to the property it is about. Run it after editing a style. Pass the style as an object, a URL or a file path.

NameTypeReqDescription
pathstring–Path to a style JSON file, relative to the directory the server runs in.
styleobject–The style as a JSON object.
urlstring–URL of a style JSON document.
NameTypeReqDescription
problemsarrayyes–

No examples provided.

Install

How do I install the maplibre-mcp server?

maplibre-mcp runs locally as an npm package, launched with npx -y maplibre-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · maplibre-mcp

# add to Claude Code
claude mcp add birkskyum-maplibre-mcp -- npx -y maplibre-mcp
Common questions

What is the maplibre-mcp server?

maplibre-mcp is listed in the public MCP registry as io.github.birkskyum/maplibre-mcp. An MCP server that lets AI agents check, render and show MapLibre styles. This page covers its npm package (maplibre-mcp).

Is the maplibre-mcp server safe to use?

maplibre-mcp scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the maplibre-mcp server expose?

maplibre-mcp exposes 13 tools: validate_style, describe_style_spec, describe_sources, inspect_tile, debug_layers, and 8 more. Their descriptions and schemas cost roughly 2,800 tokens of context every time the server is loaded.

Is the maplibre-mcp server still maintained?

maplibre-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the maplibre-mcp server under?

maplibre-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the maplibre-mcp server?

VerifyMCP ran 17 checks on maplibre-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 13 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.