MCP Server PROJ
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| transform-coordinatesA | 在不同坐标系统之间转换坐标，支持EPSG、WKT和Proj格式的坐标系统 |
| list-supported-crsB | 列出所有支持的坐标系统 |
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 2 tools
The two tools have clearly distinct purposes: one transforms coordinates between systems, the other lists supported coordinate systems. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb-noun pattern with hyphenated lowercase (transform-coordinates, list-supported-crs), making the naming predictable and easy to understand.
With only two tools, the server feels thin for a coordinate transformation service. While they cover a minimal workflow, the count is borderline and could be expanded with additional useful operations.
The core workflow is covered: users can list supported CRS and transform coordinates between them. Minor gaps exist, such as retrieving detailed CRS metadata or more advanced PROJ operations, but the basics are functional.