@zealgeo/mcp-geo-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is @zealgeo/mcp-geo-server?

@zealgeo/mcp-geo-server is a geospatial processing tool server based on the Model Context Protocol (MCP) that provides functionalities for coordinate system conversion, distance calculation, and area calculation.

How to use @zealgeo/mcp-geo-server?

To use the server, install it via npm with the command: npx -y @zealgeo/mcp-geo-server. You can then access its various tools for geospatial analysis.

Key features of @zealgeo/mcp-geo-server?

  • Supports conversion between multiple coordinate systems: BD09, GCJ02, WGS84, and Web Mercator.
  • Provides methods for calculating distances and areas based on geospatial data.
  • Allows input in various coordinate systems for flexible usage.

Use cases of @zealgeo/mcp-geo-server?

  1. Converting coordinates between different systems for mapping applications.
  2. Calculating distances for route planning and logistics.
  3. Determining areas for land use and environmental studies.

FAQ from @zealgeo/mcp-geo-server?

  • What coordinate systems are supported?

The server supports BD09, GCJ02, WGS84, and Web Mercator coordinate systems.

  • How accurate are the calculations?

The accuracy of conversions and calculations depends on the quality of the input data.

  • Is there any cost to use the server?

No, the server is open-source and free to use under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

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