qgis-map-server

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.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Infrastructure gis mapping ogc wms wfs wmts qgis server geospatial
⚙ Agent Friendliness
27
/ 100
Can an agent use this?
🔒 Security
40
/ 100
Is it safe for agents?
⚡ Reliability
32
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
0
Error Messages
0
Auth Simplicity
30
Rate Limits
0

🔒 Security

TLS Enforcement
60
Auth Strength
35
Scope Granularity
10
Dep. Hygiene
50
Secret Handling
50

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.

⚡ Reliability

Uptime/SLA
0
Version Stability
50
Breaking Changes
40
Error Recovery
40
AF Security Reliability

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.

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

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

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: No Scopes: No

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

Free tier: No
Requires CC: No

Typically self-hosted open-source software; costs are deployment/infrastructure and operational effort, not per-request licensing (based on provided info, pricing not specified).

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known 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.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for qgis-map-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered