M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionQGISMCPConnect Claude AI to QGIS Desktop via the Model Context Protocol.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS30 / 100 · D75 / 100 · B
Reliability4 / 2010 / 20
Security and permissions3 / 2016 / 20
Maintenance3 / 2018 / 20
Documentation10 / 2017 / 20
Setup experience10 / 2014 / 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.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
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 needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
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 internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
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.
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1511