Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Model Context Protocol integration documentation. #36799

Open
wants to merge 2 commits into
base: next
Choose a base branch
from

Conversation

allenporter
Copy link
Contributor

@allenporter allenporter commented Jan 8, 2025

Proposed change

Add Model Context Protocol integration documentation.

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

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.

Summary by CodeRabbit

  • New Features
    • Added support for Model Context Protocol (MCP) integration
    • Enables connection to MCP servers for enhanced conversation agent functionality
    • Supports web search and memory capabilities through MCP servers
    • Provides configuration options for connecting to MCP servers

@home-assistant home-assistant bot added has-parent This PR has a parent PR in a other repo next This PR goes into the next branch labels Jan 8, 2025
Copy link

netlify bot commented Jan 8, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 99295e8
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/677dfe8af7c56b000837d5e1
😎 Deploy Preview https://deploy-preview-36799--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

Copy link
Contributor

coderabbitai bot commented Jan 8, 2025

📝 Walkthrough

Walkthrough

The pull request introduces a new integration for the Model Context Protocol (MCP) in Home Assistant. This integration enables interaction between Home Assistant and MCP servers, focusing on enhancing conversation agent functionality through the Assist API. The documentation covers the protocol's purpose, configuration options, server connection methods, and architectural overview of how Home Assistant clients interact with MCP servers.

Changes

File Change Summary
source/_integrations/mcp.markdown Added comprehensive documentation for Model Context Protocol (MCP) integration, including configuration details, server interaction methods, and usage guidelines

Sequence Diagram

sequenceDiagram
    participant HA as Home Assistant
    participant MCP as MCP Server
    participant SSE as SSE Proxy

    HA->>MCP: Connect to MCP Server
    MCP-->>HA: Establish Connection
    HA->>SSE: Poll SSE Endpoint
    SSE-->>HA: Retrieve Available Tools
    HA->>MCP: Request Conversation Actions
    MCP-->>HA: Return Conversation Context
Loading

This sequence diagram illustrates the high-level interaction between Home Assistant, the MCP Server, and the optional SSE Proxy, demonstrating the connection and tool retrieval process for the new MCP integration.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (6)
source/_integrations/mcp.markdown (6)

49-49: Remove trailing space.

There is a trailing space at the end of line 49.

-(for example [Anthropic](/integrations/anthropic/), [Google Generative AI](/integrations/google_generative_ai_conversation), [Ollama](/integrations/ollama/), [Open AI](/integrations/openai_conversation/)). 
+(for example [Anthropic](/integrations/anthropic/), [Google Generative AI](/integrations/google_generative_ai_conversation), [Ollama](/integrations/ollama/), [Open AI](/integrations/openai_conversation/)).
🧰 Tools
🪛 Markdownlint (0.37.0)

49-49: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)


41-44: Consider providing more specific URL examples.

The current example http://example/sse could be enhanced with more realistic examples to help users understand the expected format.

-  description: The URL for the SSE endpoint of the MCP server e.g. `http://example/sse`
+  description: The URL for the SSE endpoint of the MCP server e.g. `http://localhost:8000/sse` or `http://192.168.1.100:8000/sse`

61-61: Remove trailing space.

There is a trailing space at the end of line 61.

-and directly run an MCP server as a local command line tool. You can 
+and directly run an MCP server as a local command line tool. You can
🧰 Tools
🪛 Markdownlint (0.37.0)

61-61: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)


70-75: Consider expanding the Tools section.

The Tools section could benefit from:

  1. Examples of common tools
  2. How to configure and use tools with conversation agents
  3. Best practices for tool usage

96-96: Remove extra blank line.

There are multiple consecutive blank lines that should be reduced to a single blank line.

-

-
+
🧰 Tools
🪛 Markdownlint (0.37.0)

96-96: Expected: 1; Actual: 2
Multiple consecutive blank lines

(MD012, no-multiple-blanks)


1-101: Consider adding these sections to enhance the documentation:

  1. Add a "First-time setup" section with step-by-step instructions
  2. Include example configurations for popular MCP servers
  3. Add troubleshooting examples for common issues
🧰 Tools
🪛 Markdownlint (0.37.0)

49-49: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)


61-61: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)


96-96: Expected: 1; Actual: 2
Multiple consecutive blank lines

(MD012, no-multiple-blanks)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0b328dd and 99295e8.

📒 Files selected for processing (1)
  • source/_integrations/mcp.markdown (1 hunks)
🧰 Additional context used
🪛 Markdownlint (0.37.0)
source/_integrations/mcp.markdown

49-49: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)


61-61: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)


96-96: Expected: 1; Actual: 2
Multiple consecutive blank lines

(MD012, no-multiple-blanks)

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - home-assistant-docs
  • GitHub Check: Header rules - home-assistant-docs
  • GitHub Check: Pages changed - home-assistant-docs
🔇 Additional comments (5)
source/_integrations/mcp.markdown (5)

1-16: LGTM! Frontmatter is well-structured.

The metadata is correctly configured with appropriate categories, IoT class, and related integrations.


18-27: LGTM! Clear and informative introduction.

The introduction effectively explains the purpose and benefits of the MCP integration.


28-34: LGTM! Prerequisites are clearly stated.

The requirements and additional resources are well-documented.


46-67: LGTM! Comprehensive architecture overview.

The section effectively explains the integration's architecture and its relationship with LLM conversation agents.

🧰 Tools
🪛 Markdownlint (0.37.0)

49-49: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)


61-61: Expected: 0 or 2; Actual: 1
Trailing spaces

(MD009, no-trailing-spaces)


89-101: LGTM! Clear troubleshooting and removal instructions.

The section provides helpful debugging resources and standard removal instructions.

🧰 Tools
🪛 Markdownlint (0.37.0)

96-96: Expected: 1; Actual: 2
Multiple consecutive blank lines

(MD012, no-multiple-blanks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has-parent This PR has a parent PR in a other repo next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant