htag-docs
Public HTAG discovery for MCP tools, API endpoints, OpenAPI ops, and agents.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"htag-docs": {
"url": "https://api.htagai.com/mcp/v1/servers/htag-docs/mcp"
}
}
}Remote endpoints
https://api.htagai.com/mcp/v1/servers/htag-docs/mcpstreamable-httpWhat it can do
Tool inventory
Tools (5)
🟢list_mcp_servers
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).
Input Schema
{
"type": "object",
"properties": {},
"title": "list_mcp_serversArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"items": {
"additionalProperties": true,
"type": "object"
},
"title": "Result",
"type": "array"
}
},
"required": [
"result"
],
"title": "list_mcp_serversOutput"
}🟢list_mcp_tools(server)
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.
Input Schema
{
"type": "object",
"properties": {
"server": {
"title": "Server",
"type": "string"
}
},
"required": [
"server"
],
"title": "list_mcp_toolsArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"items": {
"additionalProperties": true,
"type": "object"
},
"title": "Result",
"type": "array"
}
},
"required": [
"result"
],
"title": "list_mcp_toolsOutput"
}🟢list_api_endpoints(tag, query)
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.
Input Schema
{
"type": "object",
"properties": {
"tag": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Tag"
},
"query": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Query"
}
},
"title": "list_api_endpointsArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"items": {
"additionalProperties": true,
"type": "object"
},
"title": "Result",
"type": "array"
}
},
"required": [
"result"
],
"title": "list_api_endpointsOutput"
}🟢get_api_endpoint(path, method)
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.
Input Schema
{
"type": "object",
"properties": {
"path": {
"title": "Path",
"type": "string"
},
"method": {
"title": "Method",
"type": "string"
}
},
"required": [
"path",
"method"
],
"title": "get_api_endpointArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"anyOf": [
{
"additionalProperties": true,
"type": "object"
},
{
"type": "null"
}
],
"title": "Result"
}
},
"required": [
"result"
],
"title": "get_api_endpointOutput"
}🟢list_micro_agents
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.
Input Schema
{
"type": "object",
"properties": {},
"title": "list_micro_agentsArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"items": {
"additionalProperties": true,
"type": "object"
},
"title": "Result",
"type": "array"
}
},
"required": [
"result"
],
"title": "list_micro_agentsOutput"
}Community
Evidence