{"id":"klokantech-tileserver-gl","name":"tileserver-gl","homepage":"https://hub.docker.com/r/klokantech/tileserver-gl","repo_url":"https://hub.docker.com/r/klokantech/tileserver-gl","category":"infrastructure","subcategories":[],"tags":["gis","mapping","tiles","vector-tiles","mapbox-gl","http-server","open-source"],"what_it_does":"tileserver-gl is an open-source vector tile and raster tile server (commonly used with Mapbox/GL style inputs) that serves map tiles over HTTP, typically backed by PostGIS and/or other tile sources.","use_cases":["Serving Mapbox GL compatible vector tiles to web/mobile map frontends","Hosting raster or vector tiles for offline or performance-sensitive map applications","Building custom map backends for GIS/geo applications"],"not_for":["As a managed hosted service requiring SaaS-style guarantees","Use cases needing fine-grained user authentication/authorization out of the box for each tile request","Workloads that require strict API contract/versioning guarantees like enterprise APIs (it is primarily an application/server)"],"best_when":"You control the deployment environment and can configure the tile source(s) and networking/security controls to suit your application.","avoid_when":"You cannot provide infrastructure-level security (network controls, TLS termination, rate limiting) and want the server itself to handle all security requirements.","alternatives":["tegola","t-rex","martin","geoserver (raster-oriented)","MapTiler/other hosted tile services"],"af_score":33.2,"security_score":35.0,"reliability_score":25.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:20:58.693421+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":[],"oauth":false,"scopes":false,"notes":"No dedicated authentication mechanism is evident from the provided material; production auth is typically handled via reverse proxy/network controls (or tileserver configuration, if present in the full docs)."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source; costs are infrastructure/ops (compute, storage, database) rather than API usage pricing."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":33.2,"security_score":35.0,"reliability_score":25.0,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":70.0,"rate_limit_clarity":10.0,"tls_enforcement":70.0,"auth_strength":20.0,"scope_granularity":0.0,"dependency_hygiene":40.0,"secret_handling":50.0,"security_notes":"Security is largely deployment-dependent (TLS termination, network access controls, and proxy-based auth/rate limiting). As an open-source server, threat model should assume you manage hardening: restrict inbound traffic, enforce HTTPS, and monitor logs/metrics. No claims can be made about auth/scopes or secret handling without full repo/documentation inspection.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":30.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Treat as an HTTP tile server rather than a typical CRUD API; agent workflows should focus on URL construction and caching behavior.","Rate limiting and access control are typically implemented at the reverse proxy layer, so agent-driven traffic may need external throttling controls."]}}