- Direct MCP for clients that support
streamable_http - HoopAI MCP Proxy for clients that only support
stdio
Prerequisites
- A HoopAI Private Integration Token (PIT) or OAuth access token
- A
locationIdto scope tool calls - Scopes for the modules you plan to use (contacts, conversations, calendars, opportunities, payments, etc.)
Option A: Direct MCP (recommended)
Use this when your MCP client supports HTTP Streamable transport. EndpointAuthorization: Bearer <token>locationId: <your-location-id>
Example: LangGraph MCP client
Example: n8n MCP client
- MCP URL:
https://services.leadconnectorhq.com/mcp/ - Transport:
HTTP Streamable - Header:
AuthorizationwithBearer <token> - Provide
locationIdas header or prompt context
The official MCP docs call out
HTTP Streamable support in n8n v1.104+.Option B: HoopAI MCP Proxy (stdio)
Use this path for MCP clients that do not yet support HTTP Streamable (for example Claude Desktop).
Smoke test prompts
After setup, test with prompts like:- “Show me my last 10 contacts”
- “Find unread conversations and summarize them”
- “Check next available slots for tomorrow”
- “Move opportunity X to the next pipeline stage”
Troubleshooting
401/403: token is invalid or missing scopes.400: wrong or missinglocationId.- No tool responses in
stdioclients: use the HoopAI proxy path. - Wrong location data: explicitly set
HOOPAI_LOCATION_ID.