Connect the three HtAG MCP servers to your AI assistant

Connect your AI assistant to HtAG through three MCP servers: Docs for finding the right tools, Intelligence for property and market data, and Spatial for H3 maps and geographic analysis. This guide walks through adding all three and checking that each connection works. Claude users can find HTAG in Claude’s connector directory; Perplexity and other clients use the custom connection instructions below.

MCP lets your assistant discover and call HtAG tools inside your conversation. Your assistant handles the conversation and reasoning; HtAG supplies the documented tools and data.

Before you start

• Use an MCP client that supports remote Streamable HTTP servers.
• Sign up for the HTAG Developer Portal, or sign in if you already have a Developer Portal account. Your HTAG SaaS login will not work here: the Developer Portal is a separate platform. Select the organization with access to HTAG Intelligence and the Spatial data you need. Docs is public and needs no account or authentication.
• For custom connections in Perplexity or another client, open Agents & MCP for the current client instructions and Connect wizard. For Claude, follow the directory steps below.
• Check Billing and current pricing before retrieving data. Connecting a server and running a data workflow are separate steps.

The three connections to add

1. HtAG Docs — discover the tools

Use Docs to list available servers and tools, find REST operations, and inspect their inputs and response contracts before running a workflow.

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

Authentication: none. Add this URL as a remote MCP connection named HtAG Docs. Leave API-key and OAuth credential fields empty.

2. HtAG Intelligence — property and market data

Intelligence provides address matching, property records, suburb and LGA market data, demographics and related research tools.

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

Authentication: use the portal’s guided OAuth connection for supported clients, or the x-api-key header for a client that supports custom headers. Name this connection HtAG Intelligence.

3. HtAG Spatial — maps and geographic layers

Spatial provides H3 cell metrics, cell geometry and geographic concordance for map-based analysis. Add it separately from Intelligence so your assistant can discover both tool sets.

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

Authentication: OAuth or an x-api-key header through a supported client. Name this connection HtAG Spatial.

Connect in Claude through the connector directory

The three HTAG connectors are available in Claude’s directory. Use these listings to connect each server; the custom OAuth setup in the next section is for other clients.

1. Open Claude.ai and go to Settings → Connectors.
2. Open the connector search and search for HTAG.
3. You should see three listings: HTAG Documentation, HTAG Intelligence and HTAG Spatial.
4. Open each listing and select Connect. Follow the prompts for each connector, including HTAG sign-in and authorization where requested.
5. Connect all three one by one, then make them available in your Claude conversation.

HTAG Documentation is the directory name for the Docs server described above. It helps Claude find the right tools and understand their inputs. Intelligence supplies property and market data; Spatial supplies H3 maps and geographic layers.

Connect in Perplexity or another custom OAuth client

For a client that supports custom remote MCP connections, add the three server URLs listed above. Follow the Developer Portal instructions for that client.

1. Open Agents & MCP and select Open Connect wizard. Choose Perplexity or your supported client and follow the instructions shown.
2. In your client’s connector settings, add HtAG Docs using its URL above. It is public; leave authentication fields empty.
3. Add HtAG Intelligence using its URL. If the client requires an OAuth client ID and client secret, create the OAuth client through the portal’s wizard and enter the supplied values in the connector settings. Complete the HTAG sign-in and authorization prompts.
4. Repeat for HtAG Spatial using its own URL and the portal’s instructions for that connection.
5. Enable all three connections for your conversation. Setup screens vary between clients, so use the current portal instructions for your platform.

OAuth credentials and API keys are different authentication methods. Use the method your client supports; keep credential values in its connection settings.

Connect with the ChatGPT app

In the ChatGPT desktop app with custom MCP support, add a separate connection for each HtAG server. These instructions follow the Settings screen shown in the app; labels may vary by version.

1. Open Settings → Plugins → MCPs and choose Connect to a custom MCP.
2. Enter the connection name from the table below, then select Streamable HTTP instead of STDIO.
3. Enter the full server URL. For Intelligence and Spatial, add an HTTP header with the name x-api-key and your HtAG API key as its value. Create or retrieve your key in the Developer Portal under Authorization. Docs needs no authentication.
4. Select Save, then repeat for the other two servers.
5. Enable the three connections for your chat and follow the tool-discovery check below.

Use the key as the header value without a Bearer prefix. Keep it in the connection settings, rather than putting it in the URL or chat. The JSON example in the next section shows the equivalent URLs and headers for clients that accept mcpServers JSON; in the ChatGPT app, use its native connection fields.

Connect with Cursor or a header-based client

In the Developer Portal, open Authorization and create an API key for your integration. In Cursor, open Settings → MCP Servers, or edit ~/.cursor/mcp.json. Add the three entries below to your configuration, preserving any servers you already use.

{
  "mcpServers": {
    "htag-docs": {
      "url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
    },
    "htag": {
      "url": "https://api.htagai.com/mcp/v1/servers/htag/mcp",
      "headers": {
        "x-api-key": "YOUR_HTAG_API_KEY"
      }
    },
    "htag-spatial": {
      "url": "https://api.htagai.com/mcp/v1/servers/htag-spatial/mcp",
      "headers": {
        "x-api-key": "YOUR_HTAG_API_KEY"
      }
    }
  }
}

Replace both YOUR_HTAG_API_KEY placeholders with your own key. Docs deliberately has no key header. Save the configuration and reload or restart your client so it discovers the tools. Keep a configuration containing your key out of public repositories and shared screenshots.

Verify all three connections

Start with tool discovery, before asking for a large data extract. Paste this prompt into your assistant:

Use HtAG Docs to list the tools available on the htag and htag-spatial servers. Then show which HtAG Intelligence and HtAG Spatial tools are available in this conversation. Do not retrieve property or market data yet.

Check that Docs returns a catalogue and that Intelligence and Spatial appear in the client’s connected-tool list. A catalogue listing describes what exists; the client’s list confirms which connections are enabled for your conversation.

When ready for a small live check:

Plan a tightly bounded Richmond VIC locality lookup through HtAG Intelligence. Show the proposed inputs, expected workload and current pricing basis first. Wait for my approval before retrieving data. Do not paginate, retry or broaden the query automatically.

You can verify Spatial tool discovery without downloading a heatmap. Before a spatial data request, choose one small area, the resolution and an explicit row limit in the plan.

If a connection does not work

• No tools: check the full URL, enable the connector in the conversation and reload the client.
• Sign-in or authorization failure: reconnect through OAuth, or check the key and exact x-api-key header in a header-based client.
• Client rejects the configuration: use its native connection fields. The JSON above is for clients that accept the mcpServers format.
• Billing error during a data call: check your account balance and access in the portal before retrying.

Your setup is complete when Docs can return documentation and both authenticated servers expose their tools in your assistant. You can now choose a small workflow and review its tool plan before running it.

Next: set up the HtAG API · MCP connection reference