GDI Catalogue MCP
Related Servers
Alternatives to GDI Catalogue MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for discovering and accessing data from a GeoNetwork 4.x catalog. Enables an AI assistant to search metadata records, view details, and discover services (WMS, WFS, downloads, etc.) referenced in the catalog.3-

EEA GeoNetwork MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables interaction with the European Environment Agency (EEA) GeoNetwork Catalogue API to search, manage, and edit geographic metadata records. It supports advanced spatial searches, metadata exports in multiple formats, and authenticated updates to records and their attachments.4MIT- AlicenseNot gradedqualityBmaintenanceEnables searching, viewing metadata, and querying tabular resources from Netherlands Open Data (data.overheid.nl) via CKAN.245 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching and exploring Spain's National Open Data Catalog, letting users find datasets by title or theme, list available themes, retrieve full dataset records with publisher, license and distribution details, and obtain catalog totals via the official SPARQL endpoint. It connects over Streamable HTTP, SSE, or local stdio using the public keyless datos.gob.es API.MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching the USGS scientific data catalog and retrieving individual records or their hierarchical child items, returning summaries, categories, dates, contacts, web links, and download URLs for datasets, publications, and projects.15 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for GovData.de, Germany's national open-data portal via CKAN API, enabling AI agents to list publishing organizations and thematic groups.2 npmMIT
TDQS
Scored across 2 tools
search_records is for discovery via keywords and pagination, while get_record retrieves a specific record by its exact ID. The two purposes are clearly separated with no overlap, so an agent can easily choose the correct tool.
Both tools follow a consistent snake_case verb_noun pattern: search_records and get_record. The plural/singular noun difference reflects the operation (search many vs. get one) and does not break the pattern.
With only two tools, the surface feels thin for a CSW catalogue even though the two provided operations are focused. The count is borderline per the rubric for 1–2 tools, lacking additional conveniences like capabilities or spatial search.
The core read-only lifecycle of discovery (search) and retrieval by ID (get_record) is fully covered, including pagination hints. Minor gaps remain, such as no direct spatial/bbox search or get_capabilities operation, but agents can work around these using keyword search.