HoopAI runs on platform APIs, so the official MCP endpoint is the fastest way to get broad MCP tool coverage.
Official endpoint
https://services.leadconnectorhq.com/mcp/
Transport and auth
- Transport:
streamable_http
- Header:
Authorization: Bearer <PIT-or-OAuth-token>
- Header:
locationId: <location-id>
Scope model
MCP tool access is scope-driven. Your token must include the scopes required by each tool you call.
Start with read-only scopes first, then add write scopes for production automations.
Dynamic location patterns
You can provide location in two patterns:
- Hardcoded header in MCP client config
- Runtime user/system prompt that asks your orchestration layer for target
locationId
n8n notes
For n8n MCP client nodes:
- MCP URL:
https://services.leadconnectorhq.com/mcp/
- Transport:
HTTP Streamable
- Add
Authorization header
- Set
locationId header (or runtime context)
Sample client config
{
"ghl": {
"url": "https://services.leadconnectorhq.com/mcp/",
"transport": "streamable_http",
"headers": {
"Authorization": "Bearer your-token",
"locationId": "your-location-id"
}
}
}
Where this fits in HoopAI MCP
- Use this direct server for tool-rich MCP clients.
- Use HoopAI MCP Proxy when your client only supports
stdio.
- Build subagent routing on top for safer operations and better tool selection.
