I tried to connect newly released GHL MCP server. But their authentication requires two parameters in header, API Key and locationId, there are only Bearer and Header authentication methods, that do not allow put more params.
Hey! For APIs like GHL MCP that require multiple custom headers, you can skip the built-in auth and set both API-Key and locationId manually in the Headers section of the HTTP Request node. Just use “None” for authentication, and define both headers there — that should work fine. Let me know if you need a quick example!
1 Like
Can you please demonstrate an example for a MCP server. I know this is easy for simple http requests but not sure its possible to connect to MCP servers as a tool (client). Thanks.
HTTP request in this case has no point, as it should work as MCP server node (request tools, do other request based on tools descriptions, etc.). It should be setup as MCP node.
1 Like
Did you found any workaround on this?
Came here to say exactly this since I’m also looking to integrate the GHL MCP server.
Also will it work without the /sse on the end? The tool docs say it should use an /sse endpoint.
Yes please give us an example for setting up the MCP Client with multiple headers. I dont understand where to put exactly the expression. {
“mcpServers”: {
“prod-ghl-mcp”: {
“url”: “https://services.leadconnectorhq.com/mcp/”,
“headers”: {
“Authorization”: “Bearer your-token”,
“locationId”: “sub-account-id”
}
}
}
}