Hexagon GeoCloud MCP Server

A remote Model Context Protocol endpoint served from the Hexagon GeoCloud web property and discoverable through RFC 9728 protected-resource metadata and RFC 8414 authorization-server metadata on the same host. Two server routes are registered under the /wp-json/mcp namespace; both answer an anonymous tools/list with HTTP 401, so the tool set and its input schemas require authenticated introspection.

Other Resources

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/geocloud-mcp"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: hexagon-ab:geocloud-mcp
name: Hexagon GeoCloud MCP Server
description: A remote Model Context Protocol endpoint served from the Hexagon GeoCloud web property and
  discoverable through RFC 9728 protected-resource metadata and RFC 8414 authorization-server metadata
  on the same host. Two server routes are registered under the /wp-json/mcp namespace; both answer an
  anonymous tools/list with HTTP 401, so the tool set and its input schemas require authenticated introspection.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://geocloud.hexagon.com/
baseURL: https://geocloud.hexagon.com/wp-json/mcp/mcp-oauth-server
tags:
- MCP
- Agents
- Geospatial
properties:
- type: MCPServer
  url: mcp/hexagon-mcp.yml