Developer-Tools

HtAG Documentation

by HtAG Analytics

Overview

The htag-docs MCP server is HtAG’s public documentation and discovery layer for developers building against the HtAG API ecosystem. It lets Claude inspect which MCP servers HtAG exposes, list the tools available on each server, browse public REST endpoints, retrieve full OpenAPI operation details, and discover callable HtAG micro-agents. It is designed for developer enablement: understanding what data and capabilities exist, selecting the right endpoint or MCP tool, generating accurate integration guidance, and helping teams move from idea to working implementation without manually reading the whole API catalogue.

Tools

get_api_endpoint

Claude

Return the full OpenAPI operation for one HTAG REST endpoint — parameters, requestBody, responses, examples. Use this BEFORE recommending an endpoint so your parameter hints match the live spec. Returns null if the endpoint is not in the catalogue.

list_api_endpoints

Claude

List HTAG public REST endpoints. Optional tag (e.g. 'Markets', 'Property', 'Spatial') and query (substring against path / summary) filters. Returns path, method, operationId, tags, and summary for each match.

list_mcp_servers

Claude

List every MCP server HTAG currently exposes. Each entry includes the server name, a short description, its mount path, and whether it is public (no auth required).

list_mcp_tools

Claude

List every tool registered on a named MCP server. Use list_mcp_servers first to discover server names. Each entry includes the tool name, its description, and the JSON-Schema input.

list_micro_agents

Claude

List every callable HTAG micro-agent — turnkey agents that compose endpoint chains and apply HTAG methodology. Examples: 'suburb-analysis', 'suburb-comparison', 'comprehensive-dd'. Useful when a use case is best served by an existing agent rather than raw endpoint composition.

Links

Documentation ↗Privacy Policy ↗

App Stats

Tools

Claude

Platforms