{"id":"opengisch-qgis-server","name":"qgis-server","homepage":"https://hub.docker.com/r/opengisch/qgis-server","repo_url":"https://hub.docker.com/r/opengisch/qgis-server","category":"infrastructure","subcategories":[],"tags":["gis","geospatial","qgis","wms","wfs","map-server","ogc","spatial","server"],"what_it_does":"qgis-server is a server-side application for publishing QGIS projects as geospatial map services (e.g., OGC/WMS/WMTS/WFS/other endpoints depending on configuration). It runs HTTP services that render maps and expose spatial data capabilities based on QGIS project configuration.","use_cases":["Publish map layers from QGIS projects over the web","Serve geospatial maps to GIS clients via OGC standards","Expose spatial datasets for querying (depending on enabled services/configuration)","Create internal/external basemaps and overlays for web mapping applications"],"not_for":["As a simple file-hosting or generic REST backend","As an AI/LLM-centric API platform with first-class JSON CRUD APIs","High-throughput machine-to-machine transactional workloads (it is primarily geospatial rendering/query infrastructure)"],"best_when":"You need standards-based geospatial map/data publishing from existing QGIS projects, with GIS clients and/or OGC-compatible services.","avoid_when":"You only need lightweight non-spatial APIs; you also want strong, documented API auth/rate-limit semantics at the application layer (these are typically deployment/config dependent).","alternatives":["MapServer","GeoServer","ArcGIS Server","TServer (other OGC-focused GIS servers)","Direct tile services/CDNs with pre-rendering pipelines"],"af_score":26.5,"security_score":43.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:43:12.324228+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":["Web server authentication depending on deployment (e.g., reverse proxy, HTTP auth, OAuth/OIDC at proxy)","Service-level controls are typically configuration/authorization-chain dependent rather than a single built-in API auth method"],"oauth":false,"scopes":false,"notes":"qgis-server deployments commonly rely on front-end reverse proxies (Apache/Nginx) or container/service configuration for authentication/authorization; built-in, documented API auth mechanisms and OAuth scopes were not provided in the supplied data."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source/commodity self-hosting model (costs are infrastructure/ops-related), based on typical qgis-server usage; no pricing details were provided in the supplied content."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":26.5,"security_score":43.2,"reliability_score":37.5,"mcp_server_quality":0.0,"documentation_accuracy":20.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":40.0,"rate_limit_clarity":5.0,"tls_enforcement":60.0,"auth_strength":35.0,"scope_granularity":20.0,"dependency_hygiene":50.0,"secret_handling":55.0,"security_notes":"Security posture is heavily deployment-dependent (typically use HTTPS via reverse proxy, and implement access control/authorization at the web server or infrastructure layer). Since qgis-server auth details and secret-handling practices were not provided here, scores emphasize uncertainty and the need for defense-in-depth (TLS termination, least privilege, network controls, and careful management of QGIS project/resource permissions).","uptime_documented":0.0,"version_stability":60.0,"breaking_changes_history":40.0,"error_recovery":50.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["qgis-server endpoints and behavior vary significantly based on enabled OGC services and QGIS project settings","Because responses are often map images/tiles or XML/GML, agents may need special handling (content-type, large payloads)","Operational concerns (timeouts, caching, rendering cost) depend on server and project configuration, not a uniform API contract","Any auth/rate limiting is frequently implemented via reverse proxy/firewall rather than documented within a single qgis-server API specification"]}}