GIS Mcp Server

Created By
mahdin75a year ago
Please find the details on https://gis-mcp.com
Overview

What is GIS MCP Server?

GIS MCP Server is a Model Context Protocol (MCP) server that connects Large Language Models (LLMs) to GIS operations, enabling AI assistants to perform geospatial operations and transformations using GIS libraries like Shapely and PyProj.

How to use GIS MCP Server?

To use GIS MCP Server, install it via pip, configure it with your MCP-compatible client (like Claude Desktop or Cursor), and start the server to access various geospatial tools and operations.

Key features of GIS MCP Server?

  • Comprehensive geometric operations (intersection, union, buffer, etc.)
  • Advanced coordinate transformations and projections
  • Precise distance and area calculations
  • Spatial analysis and validation
  • Easy integration with MCP-compatible clients

Use cases of GIS MCP Server?

  1. Performing geospatial analysis in chatbots.
  2. Transforming coordinates between different CRS.
  3. Calculating geodetic distances and areas.

FAQ from GIS MCP Server?

  • What libraries does GIS MCP Server support?

Currently, it supports Shapely and PyProj for geospatial operations.

  • Is GIS MCP Server free to use?

Yes! GIS MCP Server is open-source and free to use.

  • How can I contribute to GIS MCP Server?

You can contribute by forking the repository, creating a feature branch, and submitting a pull request.

Server Config

{
  "mcpServers": {
    "gis-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "mahdin75/gis-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
10 months ago
Author Name
mahdin75
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago