{"id":"3liz-qgis-map-server","name":"qgis-map-server","homepage":"https://hub.docker.com/r/3liz/qgis-map-server","repo_url":"https://hub.docker.com/r/3liz/qgis-map-server","category":"infrastructure","subcategories":[],"tags":["gis","mapping","ogc","wms","wfs","wmts","qgis","server","geospatial"],"what_it_does":"QGIS Map Server (“qgis-map-server”) provides a web-mapping server that serves QGIS projects and geospatial layers as standards-based map outputs (e.g., WMS/WFS/WMTS) for use in GIS clients and web applications.","use_cases":["Publish QGIS projects as web map services for browsers and GIS clients","Create standards-based map endpoints (OGC) for interoperable spatial data sharing","Host geospatial layers for internal or customer-facing mapping portals"],"not_for":["A managed hosted SaaS API with a simple developer-only integration experience","General-purpose vector/feature storage or ETL pipeline replacement","Use cases requiring strict modern OAuth-based auth, fine-grained scopes, or API-key only turnkey access without infrastructure work"],"best_when":"You already operate a GIS stack and can deploy and configure a web server running QGIS Server functionality; you need OGC web map services backed by QGIS projects.","avoid_when":"You need turnkey cloud deployment, strong built-in auth/scopes guidance, or an agent-friendly programmable interface beyond typical geospatial service endpoints and server configuration.","alternatives":["GeoServer (OGC WMS/WFS/WMTS)","MapServer","ArcGIS Server","Tegola (for tiled maps)","qgis-server (closely related self-hosted GIS server approach)"],"af_score":26.8,"security_score":40.2,"reliability_score":32.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:40:35.846403+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":["Not specified in provided info; typically depends on server deployment (e.g., web server auth, basic auth, reverse proxy, or OGC service-level controls if configured)"],"oauth":false,"scopes":false,"notes":"No explicit authentication scheme (OAuth/API keys/scopes) was provided in the supplied materials, so auth support is assumed to be configuration- and deployment-dependent (e.g., via reverse proxy/web server)."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Typically self-hosted open-source software; costs are deployment/infrastructure and operational effort, not per-request licensing (based on provided info, pricing not specified)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":26.8,"security_score":40.2,"reliability_score":32.5,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":30.0,"rate_limit_clarity":0.0,"tls_enforcement":60.0,"auth_strength":35.0,"scope_granularity":10.0,"dependency_hygiene":50.0,"secret_handling":50.0,"security_notes":"Security posture is largely determined by how the server is deployed (HTTPS/TLS at reverse proxy or web server, and whether access control is configured). Because explicit, provided auth/scoping and operational guidance are not available here, fine-grained authorization and agent-safe handling of credentials cannot be confirmed.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":40.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["This is a self-hosted geospatial server; integration is largely via GIS/OGC standards and server configuration rather than simple JSON APIs.","Auth, rate limiting, and error format are typically determined by the surrounding web server/proxy and service configuration, so behavior can vary by deployment."]}}