{"id":"georchestra-geoserver","name":"geoserver","homepage":"https://hub.docker.com/r/georchestra/geoserver","repo_url":"https://hub.docker.com/r/georchestra/geoserver","category":"infrastructure","subcategories":[],"tags":["gis","geospatial","ogc","wms","wfs","wcs","server","spatial-data"],"what_it_does":"GeoServer is a server for publishing and managing geospatial data. It exposes geospatial services (commonly OGC standards such as WMS/WFS/WCS) and supports integrating with common data sources (e.g., PostGIS, shapefiles, rasters).","use_cases":["Publishing maps and geospatial layers over the web","Serving OGC-compliant services for GIS clients","Web-based data access to vector and raster datasets","Geospatial middleware to connect GIS clients to existing geodatabases"],"not_for":["General-purpose CRUD APIs unrelated to geospatial data","Use cases requiring strictly JSON-only REST APIs without GIS/OGC support","Environments where you cannot run a stateful server component"],"best_when":"You need standards-based geospatial services (e.g., WMS/WFS/WCS) from existing spatial datasets and can operate a GeoServer deployment.","avoid_when":"You only need a simple static file hosting solution or a lightweight serverless API without GIS/OGC semantics.","alternatives":["MapServer","ArcGIS Server","Kartoza GeoServer hosting / managed GeoServer services","Titiler (for raster processing) in combination with other services","QGIS Server"],"af_score":30.2,"security_score":48.2,"reliability_score":37.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:57:09.442969+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 authentication (commonly via GeoServer security configuration)","Other GeoServer security mechanisms (configured at deployment level)"],"oauth":false,"scopes":false,"notes":"GeoServer authentication/authorization capabilities are configuration-driven (typically role-based access via GeoServer security settings and/or the underlying servlet container). The exact scheme and scope granularity cannot be confirmed from 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":"GeoServer is generally open-source/self-hosted; costs depend on hosting, storage, and operational overhead rather than an API-style pricing model."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":30.2,"security_score":48.2,"reliability_score":37.5,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":0.0,"tls_enforcement":40.0,"auth_strength":55.0,"scope_granularity":35.0,"dependency_hygiene":50.0,"secret_handling":60.0,"security_notes":"Security posture depends heavily on deployment configuration (TLS termination, authentication method, and access controls). Without explicit details here, assume no strong guarantees around fine-grained scopes; ensure TLS is enforced at the reverse proxy/servlet container level and limit who can publish/modify layers.","uptime_documented":0.0,"version_stability":65.0,"breaking_changes_history":50.0,"error_recovery":35.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["GeoServer is typically operated as a service with configuration state (layers/styles/workspaces), not a stateless API","Operations semantics depend on chosen OGC endpoints and server configuration","Security and networking (auth, reverse proxy, TLS termination) are deployment-dependent"]}}