HtAG Documentation MCP Server

What is HtAG Docs MCP Server?

The HtAG Docs MCP Server is a public, no-auth MCP server from HtAG that lets an AI assistant discover HtAG's Australian property data platform: its MCP servers and tools, REST API endpoints with full OpenAPI details, and turnkey micro-agents.

HtAG is an Australian property intelligence provider. Its developer platform offers 89+ REST endpoints covering market analytics, property data, H3 spatial metrics, demographics and economics, four MCP servers with 75+ tools, and AI micro-agents for tasks such as suburb analysis. The Docs server is the free entry point: an agent can use it to work out which endpoint, tool or agent fits a use case, with parameters that match the live spec, before anyone signs up for a data plan. In Claude's directory it is listed as "HtAG Documentation".

How to use HtAG Docs MCP Server?

The Docs server needs no API key, OAuth sign-in or account. Point your client at:

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

Claude Code

claude mcp add --transport http htag-docs https://api.htagai.com/mcp/v1/servers/htag-docs/mcp

Claude Desktop and claude.ai

Add HtAG Documentation from Claude's connector directory, or open Settings → Connectors → Add custom connector and paste the URL above. No authentication step follows.

Cursor

In ~/.cursor/mcp.json:

{
  "mcpServers": {
    "htag-docs": {
      "url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
    }
  }
}

VS Code

In .vscode/mcp.json:

{
  "servers": {
    "htag-docs": {
      "type": "http",
      "url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
    }
  }
}

When you are ready to query data, HtAG's Intelligence and Spatial servers use OAuth in Claude and an x-api-key header in clients such as Cursor and ChatGPT; the main Intelligence endpoint is https://api.htagai.com/mcp/v1/servers/htag/mcp.

Key features of HtAG Docs MCP Server

• Public server: HtAG's developer docs list it with "Public" auth and "no auth required".
• Lists every MCP server HtAG exposes, with mount paths and whether each is public.
• Lists every tool on a named server, including each tool's JSON Schema input.
• Searches HtAG's public REST catalogue by tag (such as Markets, Property or Spatial) or by text.
• Returns the full OpenAPI operation for an endpoint, with parameters, request body, responses and examples.
• Lists HtAG micro-agents such as suburb analysis, suburb comparison and comprehensive due diligence.

HtAG Docs MCP Server tools

The server has five tools in two groups.

MCP discovery. list_mcp_servers returns each HtAG MCP server's name, description, mount path and public flag. list_mcp_tools takes a server name from that list and returns every tool registered on it with its input schema.

API and agent discovery. list_api_endpoints lists HtAG's public REST endpoints, optionally filtered by tag or query, and returns path, method, operationId, tags and summary. get_api_endpoint returns the full OpenAPI operation for one endpoint; its description tells the model to call it before recommending an endpoint so parameter hints match the live spec. list_micro_agents lists the callable micro-agents, such as suburb-analysis, suburb-comparison and comprehensive-dd.

Use cases of HtAG Docs MCP Server

• Planning an integration: "Which HtAG endpoints return rental yield by suburb, and what parameters do they take?"
• Writing client code: "Get the full OpenAPI spec for the locality reference endpoint and write a TypeScript fetch call."
• Choosing between data and agents: "Is there an HtAG micro-agent for comparing suburbs, or should I chain endpoints?"
• Tool inventory: "List the tools on HtAG's Spatial MCP server and their inputs."
• Evaluating the platform before signing up: "What property and market data does HtAG cover?"

Troubleshooting HtAG Docs MCP Server

• You expected property data, not documentation. This server only describes the platform. Use HtAG's Intelligence or Spatial servers, which require OAuth or an API key, for actual data.
• get_api_endpoint returns null. The endpoint isn't in the public catalogue; call list_api_endpoints with a tag or query to find the right path.
• list_mcp_tools finds nothing. Pass a server name exactly as returned by list_mcp_servers.