Replies: 2 comments 3 replies
|
I assumed this was the path to do it, we can make the setup docs more clear about it if you think it wasn't explained well enough. To be honest this is why I set up the nabu casa webhook addon, I felt that it would be much easier to use than Cloudflare after I Spent hours getting cloudfalre to work personally. |
3 replies
|
I took a different approach. I've setup Contextforge as an MCP gateway, so all my local MCPs are exposed to Contextforge and I only have to expose Contextforge to Claude through Cloudflare. Works great! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Because I need to mainly use Claude in a browser, and I do not have a public IP at home, I found that using the HA MCP add-on was a better option than using the locally installed HA MCP tool.
The issue I ran into was that my Cloudflare Tunnel was making it hard to get the MCP exposed over the public internet. This is the Cloudflare Tunnel add-on I am using
The instructions said that in these cases, you should configure the Cloudflare tunnel with a sub-domain, for example
ha-mcp.domain.com, that points to http://localhost:9583 which did not work for me.What I found worked was getting the hostname of the HA MCP Server Add-on, which is available in the Add-on Information screen. An example of what this will look like is
b37de126-ha-mcpSo you would configure the Cloudflare Tunnel HA add-on with
http://b37de126-ha-mcp:9583And then you would configure a Claude connector with
https://ha-mcp.example.com/[your_private_key_here]No port number, Cloudflare will do that translation.
I hope maybe this helps someone else, or maybe this can be used to enhance the documentation.
All reactions