GIS Data Conversion MCP

Created By
ronantakizawaa year ago
An MCP server for converting GIS filetypes (100+ Downloads)
Overview

what is GIS Data Conversion MCP?

GIS Data Conversion MCP is a Model Context Protocol (MCP) server designed to facilitate the conversion of various GIS file types, enabling LLMs to access geographic data conversion tools.

how to use GIS Data Conversion MCP?

To use this server, configure it in the MCP settings of your application (e.g., Claude Desktop) by editing the appropriate configuration file for your operating system.

key features of GIS Data Conversion MCP?

  • Reverse Geocoding: Converts coordinates to location information.
  • WKT/GeoJSON Conversion: Converts between Well-Known Text and GeoJSON formats.
  • CSV/GeoJSON Conversion: Transforms tabular data with coordinates to GeoJSON and vice versa.
  • TopoJSON/GeoJSON Conversion: Converts between GeoJSON and TopoJSON formats.
  • KML/GeoJSON Conversion: Transforms KML files to GeoJSON format.

use cases of GIS Data Conversion MCP?

  1. Converting geographic data formats for mapping applications.
  2. Integrating geographic data into machine learning models.
  3. Facilitating data interoperability between different GIS systems.

FAQ from GIS Data Conversion MCP?

  • What file formats does GIS Data Conversion MCP support?

It supports various formats including WKT, GeoJSON, CSV, TopoJSON, and KML.

  • Is there a demo available for GIS Data Conversion MCP?

Yes! Demos for reverse geocoding and TopoJSON to GeoJSON conversion are available on the project page.

  • What dependencies are required to run GIS Data Conversion MCP?

The server requires several libraries including @modelcontextprotocol/sdk, wellknown, csv2geojson, and others.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ronantakizawa
Star
2
Language
JavaScript
License
MIT license

Recommend Servers

View All
Alloy

2 days ago
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)

8 hours ago
Crevio

a day ago