HtAG Documentation

The htag-docs MCP server is HtAG’s public documentation and discovery layer for developers building against the HtAG API ecosystem.

It lets your AI 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.

MCP connector

Server URL: https://api.htagai.com/mcp/v1/servers/htag-docs/mcp
Login: None
Protocol: MCP 2025-06-18
Instructions: HtAG Documentation server (public, no API key). Use it to plan calls to the HtAG property data API and the HtAG MCP data servers before you make them.
Call ('calling-htag') before planning HtAG data calls (the same text is the resource guide://calling-htag). It covers call order for property questions (geocode with limit=1 and check the match, then get_property_summary, then a sold/rented search filtered by propertyType and bedrooms), cost rules (which operations bill per returned row and which per request; filter first; limit=1 to read total_count; no automatic pagination), paging and truncation fields (total, total_count, has_more, next_offset, _truncated), address keys and key spaces, and canonical property types.
For HtAG membership discounts (an eligible active HtAG plan, not Starter, reduces rates on supported usage once linked), read ('costs'); users link their plan in the developer portal themselves, so never ask for their HtAG password.
Before a read that could return more than about 100 rows, or any paging loop, estimate it in AUD with (or a limit=1 probe's billing receipt) and state the plan first.
Tools:
: the available guides (name, title, summary, updated).
(name): full markdown of one guide: calling-htag, costs, core-concepts.
: the rate card (AUD per unit by tier and monthly band, plan multipliers, free allowance, as-of date) and how to read the billing receipt.

Tools

Reads data8

Skills

None in the store listings or on the server

MCP connector

Server URL

https://api.htagai.com/mcp/v1/servers/htag-docs/mcp

None

Protocol

MCP 2025-06-18

Instructions

HtAG Documentation server (public, no API key). Use it to plan calls to the HtAG property data API and the HtAG MCP data servers before you make them.

Call ('calling-htag') before planning HtAG data calls (the same text is the resource guide://calling-htag). It covers call order for property questions (geocode with limit=1 and check the match, then get_property_summary, then a sold/rented search filtered by propertyType and bedrooms), cost rules (which operations bill per returned row and which per request; filter first; limit=1 to read total_count; no automatic pagination), paging and truncation fields (total, total_count, has_more, next_offset, _truncated), address keys and key spaces, and canonical property types.

For HtAG membership discounts (an eligible active HtAG plan, not Starter, reduces rates on supported usage once linked), read ('costs'); users link their plan in the developer portal themselves, so never ask for their HtAG password.

Before a read that could return more than about 100 rows, or any paging loop, estimate it in AUD with (or a limit=1 probe's billing receipt) and state the plan first.

Tools:

: the available guides (name, title, summary, updated).

(name): full markdown of one guide: calling-htag, costs, core-concepts.

: the rate card (AUD per unit by tier and monthly band, plan multipliers, free allowance, as-of date) and how to read the billing receipt.