Geoserver MCP vs Maplibre MCP
A side-by-side look at the Geoserver MCP and Maplibre MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Geoserver MCP for location services work over a hosted endpoint; choose Maplibre MCP for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Geoserver MCP when
- You need dedicated capabilities in the Location Services domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You have the keys it needs:
GEOSERVER_URL, GEOSERVER_USER, GEOSERVER_PASSWORD.
Choose Maplibre MCP when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MAPLIBRE_MCP_TOOLSETS. - You want tools like
validate_style, describe_style_spec, describe_gl_js_api.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 53/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | GEOSERVER_URLGEOSERVER_USERGEOSERVER_PASSWORD | MAPLIBRE_MCP_TOOLSETS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 95 | 2 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 15 |
| Full listing | View Geoserver MCP | View Maplibre MCP |
Tools & capabilities
Geoserver MCP tools
No tool names declared yet. Check the project README from the listing page.
Maplibre MCP tools 15
validate_styledescribe_style_specdescribe_gl_js_apidescribe_sourcesinspect_tiledebug_layersrender_stylepreview_stylerender_pagecompare_stylescompare_renderersshow_map- +3 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Geoserver MCP
{
"mcpServers": {
"mahdin75-geoserver-mcp": {
"url": "https://mcp.so/server/Geoserver%20MCP%20Server/mahdin75"
}
}
}
Maplibre MCP
{
"mcpServers": {
"maplibre-mcp": {
"command": "npx",
"args": [
"-y",
"maplibre-mcp"
],
"env": {
"MAPLIBRE_MCP_TOOLSETS": "YOUR_MAPLIBRE_MCP_TOOLSETS_HERE"
}
}
}
}
Frequently asked questions
Geoserver MCP is categorized under Location Services and uses a remote HTTP/SSE transport. Maplibre MCP belongs to Location Services and uses a local stdio subprocess. Pick Geoserver MCP for location services work and Maplibre MCP for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Geoserver MCP is listed as free. Auth: other. Maplibre MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mahdin75-geoserver-mcp and maplibre-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Geoserver MCP has a quality signal of 53/100 (Good) with 4 views, 0 installs and 95 GitHub stars. Maplibre MCP has 56/100 (Good) with 0 views, 0 installs and 2 GitHub stars.