epsg-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EPSG_LANG | No | Output language for tool definitions and descriptions. Set to 'ja' for Japanese output. Default is English ('en'). | en |
| EPSG_PACKS | No | Comma-separated list of country packs to load (e.g., 'jp,us,uk'). Available packs: 'jp' (Japan), 'us' (United States), 'uk'/'gb' (United Kingdom). By default, only the Japan pack is loaded. | jp |
| EPSG_DB_PATH | No | Path to an optional SQLite EPSG database file for access to the complete registry (10,000+ CRS). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_crsA | Search EPSG Coordinate Reference Systems (CRS) by keyword. Searchable by EPSG code, name, region name, or prefecture name. Covers Japanese JGD2011 CRS family, global WGS84, Web Mercator, and more. |
| get_crs_detailC | Get detailed information for a specific EPSG code. Includes datum, projection method, area of use, accuracy characteristics, and intended use cases. |
| list_crs_by_regionB | Get available CRS list for a region with purpose-based recommendations. Japan includes Plane Rectangular CS (Zones I-XIX), Global includes WGS84 and UTM zones. |
| recommend_crsB | Recommend the optimal CRS based on purpose and location. Supports web mapping, distance/area calculation, surveying, navigation, data exchange, etc. Full support for Japan Plane Rectangular CS (Zones I-XIX) including multi-zone regions like Hokkaido and Okinawa. |
| validate_crs_usageB | Validate whether a CRS is appropriate for a specific purpose and location. Detects deprecated CRS usage, area/distance calculation distortion issues, inappropriate zone selection for surveying, and provides improvement suggestions. |
| suggest_transformationA | Suggest transformation paths between two CRS. Covers Tokyo Datum to JGD2011, WGS84 to Plane Rectangular CS, etc. Searches multi-step paths, provides accuracy info, and warns about cumulative errors. |
| compare_crsA | Compare two CRS from various perspectives. Compares datum, projection method, area of use, accuracy, distortion characteristics, compatibility, and use case suitability. Explains which is better suited for specific purposes. |
| get_best_practicesC | Get CRS best practices for specific topics. Covers surveying in Japan, web mapping, data exchange, coordinate storage, mobile GPS, cross-border data, historical data, GIS integration, precision requirements, and projection selection. Provides recommended practices, common mistakes, and reference materials. |
| troubleshootB | Troubleshoot CRS-related problems. Diagnoses coordinate shifts (cm, m, km scale), area/distance calculation errors, data not displaying, and transformation errors. Identifies causes, provides diagnostic steps, and solutions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Every tool has a clearly distinct purpose with no ambiguity: compare_crs compares two CRS, get_best_practices provides guidelines, get_crs_detail gives detailed info, list_crs_by_region lists region-specific options, recommend_crs suggests optimal choices, search_crs searches by keywords, suggest_transformation finds transformation paths, troubleshoot diagnoses problems, and validate_crs_usage validates appropriateness. The descriptions clearly differentiate each tool's function, making misselection unlikely.
All tool names follow a consistent verb_noun pattern (e.g., compare_crs, get_best_practices, list_crs_by_region) using snake_case throughout. The verbs are descriptive and aligned with the actions (compare, get, list, recommend, search, suggest, troubleshoot, validate), creating a predictable and readable naming convention across the entire set.
With 9 tools, the count is well-scoped for the EPSG/CRS domain, covering key operations like searching, recommending, comparing, validating, troubleshooting, and providing detailed information. Each tool earns its place by addressing specific needs in coordinate reference system management, avoiding both thin coverage and overwhelming complexity.
The tool set provides complete lifecycle coverage for the EPSG/CRS domain: from discovery (search_crs, list_crs_by_region) and detailed information (get_crs_detail) to selection (recommend_crs, validate_crs_usage), comparison (compare_crs), transformation (suggest_transformation), troubleshooting (troubleshoot), and best practices (get_best_practices). There are no obvious gaps, ensuring agents can handle end-to-end workflows without dead ends.