Skip to content

Clarify URL configuration for MCP server#45663

Draft
samhopwell wants to merge 1 commit into
home-assistant:currentfrom
samhopwell:current
Draft

Clarify URL configuration for MCP server#45663
samhopwell wants to merge 1 commit into
home-assistant:currentfrom
samhopwell:current

Conversation

@samhopwell

Copy link
Copy Markdown

Proposed change

This PR adds a note to clarify where to get the Home Assistant URL from. If you're using a custom domain with Home Assistant Cloud, that won't work for the authorisation from something like Claude. You need to use the URL specified from Home Assistant Cloud/what is configured within your Home Assistant instance.

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

  • Link to parent pull request in the codebase:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue: fixes #

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Copilot AI review requested due to automatic review settings May 31, 2026 07:15
@samhopwell samhopwell requested a review from allenporter as a code owner May 31, 2026 07:15
@home-assistant home-assistant Bot added the current This PR goes into the current branch label May 31, 2026
@netlify

netlify Bot commented May 31, 2026

Copy link
Copy Markdown

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit e6d520c
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/6a1be017a5872200082fce73
😎 Deploy Preview https://deploy-preview-45663--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds guidance to the MCP Server integration docs to prevent OAuth login failures when configuring Claude for Desktop with a remote custom connector by clarifying which Home Assistant URL must be used.

Changes:

  • Adds a documentation note instructing users to use the configured Home Assistant external URL (including Nabu Casa Cloud URL where applicable).
  • Explains why using alternate/internal URLs can break OAuth redirect behavior (blank 404 during login).
  • Points users to the UI location to verify/update the external URL setting.

When using a remote custom connector in Claude for Desktop, the connection is brokered through Anthropic's cloud infrastructure. This means your Home Assistant instance must be publicly accessible from the internet.

{% note %}
Use the same URL that is configured as your Home Assistant external URL. If you use [Home Assistant Cloud](/integrations/cloud/), use your Nabu Casa Cloud URL (for example, `https://<your_id>.ui.nabu.casa`). Connecting with a different URL, such as an internal split-horizon domain, can cause the login step to fail with a blank 404 page, because Home Assistant builds the OAuth redirect from the configured external URL. You can check or update this URL at {% my network title="**Settings** > **System** > **Network**" %}.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So above we say "This means your Home Assistant instance must be publicly accessible from the internet". and below we says <your_home_assistant_external_url>.

Perhaps we can edit one of these points and link to https://www.home-assistant.io/docs/configuration/remote/ if users don't know what their external URL is?

@c0ffeeca7 c0ffeeca7 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm drafting this PR, as changes are needed. https://github.com/home-assistant/home-assistant.io/pull/45663/changes#r3331042642

Please undraft it once the changes have been implemented and the PR is ready for review again.

@home-assistant home-assistant Bot marked this pull request as draft June 1, 2026 05:00
@home-assistant

home-assistant Bot commented Jun 1, 2026

Copy link
Copy Markdown

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

current This PR goes into the current branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants