STAC MCP Server
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_rootC | Return the STAC root document for a catalog. |
| get_conformanceC | Return server conformance classes. |
| get_capabilitiesA | Return a summary of STAC API capabilities. Maps conformance classes to human-readable capability names, making it easier for agents to discover what features a catalog supports (e.g., query, sort, fields, aggregations). |
| search_collectionsC | Return a page of STAC collections. |
| get_collectionB | Fetch a single STAC Collection by id. |
| get_itemA | Get a specific STAC Item by collection and item ID. |
| search_itemsC | Search for STAC items. |
| estimate_data_sizeC | Estimate the data size for a STAC query. |
| get_queryablesA | Get the queryable properties for a specific STAC collection by its ID. |
| get_aggregationsC | Get aggregations for STAC items. |
| get_sensor_registry_infoA | Get information about the STAC sensor registry. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| sensor_registry_info_prompt | Information about the STAC sensor registry |
| stac_tool_overview_prompt | Overview of STAC tools available |
| tool_get_root_prompt | Usage for get_root tool |
| tool_get_conformance_prompt | Usage for get_conformance tool |
| tool_search_collections_prompt | Usage for search_collections tool |
| tool_get_collection_prompt | Usage for get_collection tool |
| tool_get_item_prompt | Usage for get_item tool |
| tool_search_items_prompt | Usage for search_items tool |
| tool_estimate_data_size_prompt | Usage for estimate_data_size tool |
| tool_get_queryables_prompt | Usage for get_queryables tool |
| tool_get_aggregations_prompt | Usage for get_aggregations tool |
| tool_ordering_info_prompt | Information on tool ordering and usage |
| catalog_discovery_prompt | Steps to discover what a STAC catalog supports |
| collection_alias_resolution_prompt | How to resolve collection id aliases across catalogs |
| estimate_size_strategy_prompt | Safe strategies for estimating data size at scale |
| explain_tool_output_prompt | Summarize and explain tool outputs for humans |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools are clearly distinct, but get_conformance and get_capabilities have some overlap in purpose (both describe server capabilities). However, get_capabilities maps to human-readable names, providing enough differentiation. Other tools like search_collections vs get_collection and search_items vs get_item are well separated.
All tool names follow a consistent verb_noun pattern using 'get_' or 'search_' prefixes with snake_case. The naming is predictable and uniform across the entire tool set.
With 11 tools, the server is well-scoped for a STAC API. Each tool serves a distinct purpose without being excessive or too sparse, covering the essential operations expected from a STAC catalog.
The tool set covers the standard STAC API surface including root, conformance, capabilities, collections, items, search, queryables, and aggregations. It also adds useful extras like data size estimation and sensor registry info, leaving no significant gaps for typical STAC workflows.