QGISMCP for VS Code: Setup & Config

What you can do with QGISMCP in VS Code

A live QGIS bridge spanning layer operations, processing algorithms, custom code, and map output.

• Create and save GIS projects through Claude.
• Run Processing Toolbox algorithms with selected parameters.

Before you start: QGISMCP in VS Code

• QGIS 3.x; README testing was limited to 3.22
• Python 3.10 or later
• uv
• Claude Desktop
• The enabled QGIS MCP plugin and its running socket server

Replace the documented absolute-path placeholder with the checkout location. Copy qgis_mcp_plugin into the active profile's plugins directory, restart QGIS, enable it, then use its Start Server action. No required environment variables are stated.

QGISMCP VS Code configuration

1. Choose VS Code configuration scope

   For QGISMCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add QGISMCP to VS Code

   Use the qgis_mcp entry below in servers. Keep QGISMCP's documented stdio connection fields and your other VS Code entries.

3. Check QGISMCP in VS Code

   QGISMCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "qgis_mcp": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "--directory",
        "/ABSOLUTE/PATH/TO/PARENT/REPO/FOLDER/qgis_mcp/src/qgis_mcp",
        "run",
        "qgis_mcp_server.py"
      ],
      "env": {}
    }
  }
}

QGISMCP tools available to VS Code

QGISMCP's stored tool list documents 15 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

ping

Look for ping among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

get_qgis_info

Look for get_qgis_info among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

Inspect details of the running QGIS installation.

load_project

Look for load_project among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

Open a project from a supplied filesystem path.

create_new_project

Look for create_new_project among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

Create and save a new QGIS project.

get_project_info

Look for get_project_info among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

Inspect information about the active project.

add_vector_layer

Look for add_vector_layer among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

add_raster_layer

Look for add_raster_layer among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

get_layers

Look for get_layers among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

remove_layer

Look for remove_layer among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

Remove a layer using its identifier.

zoom_to_layer

Look for zoom_to_layer among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

Set the map view to a layer's extent.

get_layer_features

Look for get_layer_features among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

Read vector-layer features with an optional result limit.

execute_processing

Look for execute_processing among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

Run a Processing Toolbox algorithm using supplied parameters.

save_project

Look for save_project among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

render_map

Look for render_map among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

execute_code

Look for execute_code among VS Code's agent-mode tools after starting QGISMCP through the MCP controls.

QGISMCP: full stored tool descriptions

Troubleshooting QGISMCP in VS Code

• Make uv available in the workspace, container, or remote environment hosting QGISMCP. Start through VS Code's MCP controls; inspect output and trust prompts.
• QGISMCP uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Requires manual plugin installation and starting its server in QGIS.
• Known limitation: The README reports testing only on QGIS 3.22.
• Known limitation: Arbitrary Python execution carries an explicit caution in the README.
• General VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions