Loading...
npx -y @smithery/cli install @mahdin75/geoserver-mcp --client claude{
"mcpServers": {
"geoserver-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GEOSERVER_URL=http://localhost:8080/geoserver",
"-e",
"GEOSERVER_USER=admin",
"-e",
"GEOSERVER_PASSWORD=geoserver",
"-p",
"8080:8080",
"mahdin75/geoserver-mcp"
]
}
}
}list_workspacesLists available workspaces in the GeoServer instance.
Read-only operation; no data modification.
create_workspaceCreates a new workspace in GeoServer.
Creates a new workspace, but doesn't modify existing data.
create_datastoreCreates a new datastore in a specified workspace.
Adds a new datastore, but doesn't modify existing data.
create_featurestoreCreates a new featurestore in the specified workspace.
Adds a new featurestore, but doesn't modify existing data.
create_gpkg_datastoreCreates a GeoPackage datastore in GeoServer.
Creates a new datastore; no modification of existing data.
create_shp_datastoreCreates a shapefile datastore in GeoServer.
Creates a new datastore; no modification of existing data.
The GeoServer MCP server offers a convenient way to integrate LLMs with geospatial data. However, the ability to perform write operations and the reliance on GeoServer's authentication mechanisms necessitate careful configuration and monitoring. It's relatively safe for read-only operations, but risky if write access is granted without proper controls.