| FMRS | 30 / 100 · D | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 4 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 3 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 3 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 10 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 10 / 20 | 15 / 20 | 17 / 20 |
|---|
| Best for | - GIS users and developers who want to leverage Claude AI for natural language interaction and automation of QGIS tasks.
- Those familiar with QGIS and Python who want to streamline their workflows.
- Users needing to automate complex GIS operations such as loading layers, running processing algorithms, and generating maps.
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
|
|---|
| Not for | - Users expecting a server that works without a local QGIS installation.
- Beginners unfamiliar with QGIS and PyQGIS.
- Users requiring production-grade or enterprise support.
- Those who need remote or cloud-based GIS capabilities.
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
|
|---|
| Required permissions | - File system access: load and save projects, read layer files, render maps.
- Network access: socket communication between the MCP server and the QGIS plugin.
- Code execution: execute_code allows arbitrary Python code in the QGIS environment, subject to QGIS's permissions.
| - Requires HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
| - Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
|
|---|
| Risks and side effects | - Arbitrary code execution poses security risks; malicious prompts could cause data loss or system damage.
- Potential overwriting of projects or output files, especially when processing large datasets.
- The communication between the QGIS plugin and MCP server is not encrypted and could be intercepted on a local network.
- The plugin and server are not officially endorsed by QGIS or Claude; they may have bugs or lack maintenance.
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
|
|---|
| Supported clients | Claude Desktop | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 15 | 26 | 11 |
|---|