{"id":"kartoza-geoserver","name":"geoserver","homepage":"https://hub.docker.com/r/kartoza/geoserver","repo_url":"https://hub.docker.com/r/kartoza/geoserver","category":"infrastructure","subcategories":[],"tags":["geospatial","gis","ogc","wms","wfs","wcs","mapping","server","open-source"],"what_it_does":"GeoServer is an open-source server for publishing and sharing geospatial data. It exposes GIS layers through standard OGC services (e.g., WMS/WFS/WCS) and supports styling and formats for common spatial workflows.","use_cases":["Publish GIS layers as OGC services (WMS/WFS/WCS)","Serve tiled or styled map outputs to web clients","Expose vector data for spatial queries and downloads (WFS)","Integrate geospatial data sources into a consistent publishing service","Build geospatial data infrastructures for internal or public mapping sites"],"not_for":["High-frequency low-latency APIs where you need a lightweight JSON/REST-only interface","Use-cases requiring SaaS-style managed hosting without operating the server","Systems that need strict data-plane multi-tenant isolation without additional deployment controls"],"best_when":"You need standards-based geospatial publishing (OGC) and can run/manage an application server (often with a backing data store) to serve map/vector/raster services.","avoid_when":"You cannot provide appropriate infrastructure/security hardening (network controls, TLS, authn/authz, and server resource limits) or you only need a simple non-GIS API.","alternatives":["MapServer","QGIS Server","ArcGIS Server","Terria/other front-ends paired with a GIS publishing backend","geospatial-specific managed APIs (varies by vendor)"],"af_score":29.2,"security_score":52.5,"reliability_score":45.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:39:58.562089+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["HTTP Basic (common in OGC service deployments)","Form-based authentication / container auth (deployment-dependent)","Role-based access control via GeoServer security integration (deployment-dependent)"],"oauth":false,"scopes":false,"notes":"AuthN/AuthZ in GeoServer is typically configured via built-in security and integration with the deployment environment; the exact mechanisms depend on GeoServer configuration and how it is deployed (e.g., reverse proxy, app server, or external identity provider). No OAuth/scopes are implied by the provided information."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source; pricing depends on operational infrastructure and any commercial support/licenses you may purchase."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":29.2,"security_score":52.5,"reliability_score":45.0,"mcp_server_quality":0.0,"documentation_accuracy":35.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":10.0,"tls_enforcement":70.0,"auth_strength":55.0,"scope_granularity":35.0,"dependency_hygiene":45.0,"secret_handling":55.0,"security_notes":"Security depends heavily on deployment hardening (TLS termination, authentication/authorization configuration, network controls, and limiting expensive queries). GeoServer is widely deployed but is not inherently managed as a SaaS with turnkey security controls; careful configuration is required.","uptime_documented":40.0,"version_stability":55.0,"breaking_changes_history":45.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["GeoServer service operations are often parameter-heavy (OGC requests); agents may struggle without careful request construction","Operational endpoints and auth behavior may vary significantly depending on deployment (reverse proxy/app server/security config)","Long-running requests (e.g., complex WFS queries) can fail due to server-side timeouts; retry logic may require idempotency and caching considerations","Layer styling/data-source configuration is frequently the real complexity, not the transport API itself"]}}