{"id":"opengisch-qgis-server","name":"qgis-server","af_score":26.5,"security_score":43.2,"reliability_score":37.5,"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.","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).","last_evaluated":"2026-04-04T19:43:12.324228+00:00","has_mcp":false,"has_api":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"],"has_free_tier":false,"known_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"],"error_quality":0.0}