Add documentation for Model Context Protocol Server integration #36577
Conversation
home-assistant
bot
added
has-parent
|
It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the |
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
📝 WalkthroughWalkthroughThe pull request introduces a new documentation file for the Model Context Protocol (MCP) Server integration in Home Assistant. The documentation explains how the integration enables Home Assistant to serve as a context provider for Large Language Model (LLM) client applications. It covers the integration's purpose, configuration options, architecture, client setup, and usage guidelines, including details about access control, supported functionalities, and potential limitations. Changes
Sequence DiagramsequenceDiagram
participant LLM Client
participant MCP Server
participant Home Assistant
LLM Client->>MCP Server: Request Context
MCP Server->>Home Assistant: Retrieve Entity States
Home Assistant-->>MCP Server: Return Entity Information
MCP Server-->>LLM Client: Provide Contextual Data
This sequence diagram illustrates the basic interaction between an LLM client, the MCP Server, and Home Assistant. The client requests context, the MCP Server retrieves entity states from Home Assistant, and then provides the contextual data back to the client. 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (4)
source/_integrations/mcp_server.markdown (4)
85-85: Add missing example for Claude Desktop configurationThe TODO comment indicates that an example configuration for Claude Desktop is missing. This example would be valuable for users trying to set up the integration.
Would you like me to help draft an example configuration section for Claude Desktop?
39-43: Consider expanding configuration options documentationThe configuration section could benefit from additional details about:
- Available API capabilities and limitations
- Examples of common use cases
- Security considerations for exposed entities
91-98: Consider adding specific examples of prompts and toolsTo help users better understand the integration's capabilities, consider adding:
- Concrete examples of common prompts
- Examples of available tools and their usage
- Code snippets demonstrating tool interactions
28-28: Fix markdown formattingRemove the space inside the link text for better markdown consistency.
-[MCP client ](https://modelcontextprotocol.io/clients) +[MCP client](https://modelcontextprotocol.io/clients)🧰 Tools
🪛 Markdownlint (0.37.0)
28-28: null
Spaces inside link text(MD039, no-space-in-links)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
source/_integrations/mcp_server.markdown(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/mcp_server.markdown
[uncategorized] ~47-~47: This expression is usually spelled with a hyphen.
Context: ... provide similar functionality as other LLM based conversation agents (for example [Anthr...
(BASED_HYPHEN)
[uncategorized] ~48-~48: Possible missing article found.
Context: ...ation/)). In those conversation agents, Home Assistant is the client and prepares th...
(AI_HYDRA_LEO_MISSING_THE)
[grammar] ~51-~51: The verb form ‘follow’ does not seem to match the subject ‘Protocol’.
Context: ...h a prompt. The Model Context Protocol follow a different pattern: An LLM application...
(SUBJECT_VERB_AGREEMENT)
🪛 Markdownlint (0.37.0)
source/_integrations/mcp_server.markdown
28-28: null
Spaces inside link text
(MD039, no-space-in-links)
allenporter
removed
the
needs-rebase
|
It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the |
home-assistant
bot
added
the
needs-rebase
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (3)
source/_integrations/mcp_server.markdown (3)
26-31: Fix formatting and enhance structureThe prerequisites section has a formatting issue and could be more structured.
-1. You will need an [MCP client ](https://modelcontextprotocol.io/clients) LLM Application such as [Claude Desktop](https://claude.ai/download). -1. Since most clients do not support native remote servers, you will need an additional local MCP server remote gateway. +1. An [MCP client](https://modelcontextprotocol.io/clients) LLM Application + - For example: [Claude Desktop](https://claude.ai/download) +2. A local MCP server (remote gateway) + - Required because most clients don't support native remote servers🧰 Tools
🪛 Markdownlint (0.37.0)
28-28: null
Spaces inside link text(MD039, no-space-in-links)
51-53: Fix typo in external linkThere's a typo in the link to the MCP introduction page.
-[Model Context Protocol Introducton] +[Model Context Protocol Introduction]
87-104: Consider adding practical examplesWhile the functionality section covers the basics, it would be more helpful with practical examples of:
- Common prompts that users might want to implement
- Typical tools and their usage scenarios
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
source/_integrations/mcp_server.markdown(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/mcp_server.markdown
[uncategorized] ~47-~47: This expression is usually spelled with a hyphen.
Context: ... provide similar functionality as other LLM based conversation agents (for example [Anthr...
(BASED_HYPHEN)
[uncategorized] ~48-~48: Possible missing article found.
Context: ...ation/)). In those conversation agents, Home Assistant is the client and prepares th...
(AI_HYDRA_LEO_MISSING_THE)
🪛 Markdownlint (0.37.0)
source/_integrations/mcp_server.markdown
28-28: null
Spaces inside link text
(MD039, no-space-in-links)
🔇 Additional comments (3)
source/_integrations/mcp_server.markdown (3)
18-24: Well-structured introduction with clear examples
The introduction effectively explains the integration's purpose and provides concrete examples of its usage.
35-43: Configuration section is well-documented
The configuration options are clearly explained with proper use of Home Assistant's configuration templates.
105-109: Removal instructions are properly documented
The section correctly uses the standard Home Assistant template for removal instructions.
| a local MCP server. It is recommended to get another server working first before | ||
| configuring Home Assistant MCP Server. | ||
|
|
||
| TODO: Give example |
There was a problem hiding this comment.
Add the missing example configuration
The TODO comment indicates that an example configuration is needed. This should be completed before merging.
Would you like me to help generate an example configuration for the Claude Desktop setup?
home-assistant
bot
removed
the
needs-rebase
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (4)
source/_integrations/mcp_server.markdown (4)
18-24: Fix grammatical issues in the overview section.Add a comma for better readability.
-You can control what devices and entities it can access from the {% my voice_assistants title="exposed entities page" %}. +You can control what devices and entities it can access from the {% my voice_assistants title="exposed entities page" %}.
28-28: Fix space in link text.Remove the space after "MCP client" in the link.
-You will need an [MCP client ](https://modelcontextprotocol.io/clients) +You will need an [MCP client](https://modelcontextprotocol.io/clients)🧰 Tools
🪛 Markdownlint (0.37.0)
28-28: null
Spaces inside link text(MD039, no-space-in-links)
47-48: Improve readability with proper hyphenation.Add hyphen to "LLM-based" for consistency.
-This integration can provide similar functionality as other LLM based conversation +This integration can provide similar functionality as other LLM-based conversation🧰 Tools
🪛 LanguageTool
[uncategorized] ~47-~47: This expression is usually spelled with a hyphen.
Context: ... provide similar functionality as other LLM based conversation agents (for example [Anthr...(BASED_HYPHEN)
[uncategorized] ~48-~48: Possible missing article found.
Context: ...ation/)). In those conversation agents, Home Assistant is the client and prepares th...(AI_HYDRA_LEO_MISSING_THE)
188-192: Fix list indentation in troubleshooting section.Correct the indentation of list items for consistency.
- - `Client error '404 Not Found' for url 'http://localhost:8123/mcp_server/sse'`: - this means the MCP Server integration is not configured in Home Assistant. - - - `Client error '401 Unauthorized' for url 'http://localhost:8123/mcp_server/sse'`: - this means that the long live access token is not correct. + - `Client error '404 Not Found' for url 'http://localhost:8123/mcp_server/sse'`: + this means the MCP Server integration is not configured in Home Assistant. + + - `Client error '401 Unauthorized' for url 'http://localhost:8123/mcp_server/sse'`: + this means that the long live access token is not correct.🧰 Tools
🪛 LanguageTool
[uncategorized] ~188-~188: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means the MCP Server integra...(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~191-~191: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means that the long live acce...(UNLIKELY_OPENING_PUNCTUATION)
🪛 Markdownlint (0.37.0)
188-188: Expected: 1; Actual: 2
Spaces after list markers(MD030, list-marker-space)
191-191: Expected: 1; Actual: 2
Spaces after list markers(MD030, list-marker-space)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
source/images/integrations/mcp_server/claude-todo-list-control.pngis excluded by!**/*.png
📒 Files selected for processing (1)
source/_integrations/mcp_server.markdown(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/mcp_server.markdown
[uncategorized] ~47-~47: This expression is usually spelled with a hyphen.
Context: ... provide similar functionality as other LLM based conversation agents (for example [Anthr...
(BASED_HYPHEN)
[uncategorized] ~48-~48: Possible missing article found.
Context: ...ation/)). In those conversation agents, Home Assistant is the client and prepares th...
(AI_HYDRA_LEO_MISSING_THE)
[uncategorized] ~97-~97: “the” seems less likely than “to”.
Context: .... Visit Settings… and Developer tab the click Edit Config which will edit ...
(AI_HYDRA_LEO_CP_THE_TO)
[uncategorized] ~99-~99: Possible missing comma found.
Context: ...e location depends on your operating system macOS or Windows. 1. Add a new MCP ser...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~123-~123: Possible missing comma found.
Context: ...You can then use Claude to control Home Assistant similar to how you control Home Assista...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~166-~166: You have already used ‘trying to’ in nearby sentences. Consider using one of the replacements to let your writing stand out.
Context: ...ach to MCP server home-assistant" When trying to configure a client like Claude Desktop ...
(REP_TRY)
[typographical] ~176-~176: After the expression ‘for example’ a comma is usually used.
Context: ...rst check debug logs on the client. For example in Claude for Desktop: 1. Visit *Setti...
(COMMA_FOR_EXAMPLE)
[uncategorized] ~188-~188: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means the MCP Server integra...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~191-~191: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means that the long live acce...
(UNLIKELY_OPENING_PUNCTUATION)
🪛 Markdownlint (0.37.0)
source/_integrations/mcp_server.markdown
59-59: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
92-92: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
127-127: Expected: 1; Actual: 2
Multiple consecutive blank lines
(MD012, no-multiple-blanks)
188-188: Expected: 1; Actual: 2
Spaces after list markers
(MD030, list-marker-space)
191-191: Expected: 1; Actual: 2
Spaces after list markers
(MD030, list-marker-space)
28-28: null
Spaces inside link text
(MD039, no-space-in-links)
🪛 Gitleaks (8.21.2)
source/_integrations/mcp_server.markdown
112-112: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.
(generic-api-key)
🔇 Additional comments (2)
source/_integrations/mcp_server.markdown (2)
1-16: LGTM: Frontmatter is well-structured and accurate.
The metadata is properly configured with appropriate categories, release version, and integration type.
128-144: LGTM: Clear documentation of features and limitations.
The section effectively communicates the supported functionality and current limitations.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (3)
source/_integrations/mcp_server.markdown (3)
18-22: Enhance clarity with proper hyphenation-The [Model Context Protocol](https://modelcontextprotocol.io) is an open protocol for standardizing how applications provide context to LLMs. The **Model Context Protocol Server** integration enables using Home Assistant as context for MCP LLM Client Applications. +The [Model Context Protocol](https://modelcontextprotocol.io) is an open protocol for standardizing how applications provide context to LLMs. The **Model Context Protocol Server** integration enables using Home Assistant as context for MCP LLM-based client applications.
47-49: Improve readability with proper article usage and hyphenation-This integration can provide similar functionality as other LLM based conversation -agents (for example [Anthropic](/integrations/anthropic/), [Google Generative AI](/integrations/google_generative_ai_conversation), [Ollama](/integrations/ollama/), [Open AI](/integrations/openai_conversation/)). In those conversation agents, Home Assistant is the +This integration can provide similar functionality as other LLM-based conversation +agents (for example, [Anthropic](/integrations/anthropic/), [Google Generative AI](/integrations/google_generative_ai_conversation), [Ollama](/integrations/ollama/), [OpenAI](/integrations/openai_conversation/)). In those conversation agents, Home Assistant is the🧰 Tools
🪛 LanguageTool
[uncategorized] ~47-~47: This expression is usually spelled with a hyphen.
Context: ... provide similar functionality as other LLM based conversation agents (for example [Anthr...(BASED_HYPHEN)
[uncategorized] ~48-~48: You might be missing the article “the” here.
Context: ...ation/)). In those conversation agents, Home Assistant is the client and prepares th...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
188-193: Fix list formatting and punctuation- - `Client error '404 Not Found' for url 'http://localhost:8123/mcp_server/sse'`: - this means the MCP Server integration is not configured in Home Assistant. - - - `Client error '401 Unauthorized' for url 'http://localhost:8123/mcp_server/sse'`: - this means that the long live access token is not correct. + - `Client error '404 Not Found' for url 'http://localhost:8123/mcp_server/sse'`: + This means the MCP Server integration is not configured in Home Assistant. + + - `Client error '401 Unauthorized' for url 'http://localhost:8123/mcp_server/sse'`: + This means that the long-lived access token is not correct.🧰 Tools
🪛 LanguageTool
[uncategorized] ~188-~188: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means the MCP Server integra...(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~191-~191: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means that the long live acce...(UNLIKELY_OPENING_PUNCTUATION)
🪛 Markdownlint (0.37.0)
188-188: Expected: 1; Actual: 2
Spaces after list markers(MD030, list-marker-space)
191-191: Expected: 1; Actual: 2
Spaces after list markers(MD030, list-marker-space)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
source/_integrations/mcp_server.markdown(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/mcp_server.markdown
[uncategorized] ~47-~47: This expression is usually spelled with a hyphen.
Context: ... provide similar functionality as other LLM based conversation agents (for example [Anthr...
(BASED_HYPHEN)
[uncategorized] ~48-~48: You might be missing the article “the” here.
Context: ...ation/)). In those conversation agents, Home Assistant is the client and prepares th...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~99-~99: A comma might be missing here.
Context: ...e location depends on your operating system macOS or Windows. 1. Add a new MCP ser...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[uncategorized] ~101-~101: You might be missing the article “the” here.
Context: ...or Windows. 1. Add a new MCP server to json file. You will need to set the `SSE_URL...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[style] ~166-~166: You have already used ‘trying to’ in nearby sentences. Consider using one of the replacements to let your writing stand out.
Context: ...ach to MCP server home-assistant" When trying to configure a client like Claude Desktop ...
(REP_TRY)
[typographical] ~176-~176: After the expression ‘for example’ a comma is usually used.
Context: ...rst check debug logs on the client. For example in Claude for Desktop: 1. Visit *Setti...
(COMMA_FOR_EXAMPLE)
[uncategorized] ~188-~188: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means the MCP Server integra...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~191-~191: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means that the long live acce...
(UNLIKELY_OPENING_PUNCTUATION)
🪛 Markdownlint (0.37.0)
source/_integrations/mcp_server.markdown
59-59: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
92-92: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
127-127: Expected: 1; Actual: 2
Multiple consecutive blank lines
(MD012, no-multiple-blanks)
188-188: Expected: 1; Actual: 2
Spaces after list markers
(MD030, list-marker-space)
191-191: Expected: 1; Actual: 2
Spaces after list markers
(MD030, list-marker-space)
28-28: null
Spaces inside link text
(MD039, no-space-in-links)
🔇 Additional comments (3)
source/_integrations/mcp_server.markdown (3)
1-16: LGTM! Front matter is well-structured and accurate.
The metadata is properly configured with appropriate values for the Model Context Protocol Server integration.
35-43: LGTM! Configuration section is clear and well-structured.
The configuration options are properly documented using the standard Home Assistant configuration block format.
128-145: LGTM! Clear documentation of features and limitations.
The section effectively communicates the integration's capabilities and current limitations.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (7)
source/_integrations/mcp_server.markdown (7)
1-21: LGTM! Consider enhancing the overview with an example use case.The frontmatter and overview are well-structured. Consider adding a brief example scenario in the overview to help users quickly understand the practical benefits of this integration.
Add a sentence like:
"For instance, you could ask Claude 'What's the temperature in my living room?' and it would use Home Assistant's context to provide accurate information."
22-40: Add version requirements and entity control examples.Consider enhancing this section with:
- Minimum version requirements for MCP clients
- Examples of entity types that can be controlled (lights, switches, etc.)
41-58: Consider adding an architecture diagram.The architecture overview would benefit from a visual diagram showing the relationship between Home Assistant, MCP server, and LLM clients.
Would you like me to help create a Mermaid diagram to illustrate this architecture?
🧰 Tools
🪛 LanguageTool
[uncategorized] ~44-~44: Possible missing article found.
Context: ...ation/)). In those conversation agents, Home Assistant is the client and prepares th...(AI_HYDRA_LEO_MISSING_THE)
🪛 Markdownlint (0.37.0)
55-55: Expected: 0 or 2; Actual: 1
Trailing spaces(MD009, no-trailing-spaces)
65-75: Add security considerations for access tokens.Consider adding security warnings about:
- Token scope limitations
- Regular token rotation practices
- Security implications of exposing entities
134-144: Add context for unsupported features.Consider adding brief explanations for why each unsupported feature is currently not available and if/when support might be added in the future.
146-196: Add logging configuration instructions.Consider adding:
- How to enable debug logging for the integration
- Location of Home Assistant logs relevant to this integration
- Common log patterns to look for when troubleshooting
🧰 Tools
🪛 LanguageTool
[uncategorized] ~148-~148: Possible missing comma found.
Context: ...ubleshooting information for Claude for Desktop since it is the primary client. Also se...(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~169-~169: You have already used ‘trying to’ in nearby sentences. Consider using one of the replacements to let your writing stand out.
Context: ...ach to MCP server Home Assistant" When trying to configure a client like Claude Desktop ...(REP_TRY)
[typographical] ~179-~179: After the expression ‘for example’ a comma is usually used.
Context: ...rst check debug logs on the client. For example in Claude for Desktop: 1. Visit *Setti...(COMMA_FOR_EXAMPLE)
[uncategorized] ~191-~191: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means the MCP Server integrat...(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~194-~194: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means that the long live acce...(UNLIKELY_OPENING_PUNCTUATION)
198-202: Add cleanup instructions.Consider adding steps for:
- Removing associated access tokens
- Cleaning up client configurations
- Removing any persistent data
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
source/_integrations/mcp_server.markdown(1 hunks)
🧰 Additional context used
🪛 LanguageTool
source/_integrations/mcp_server.markdown
[uncategorized] ~44-~44: Possible missing article found.
Context: ...ation/)). In those conversation agents, Home Assistant is the client and prepares th...
(AI_HYDRA_LEO_MISSING_THE)
[uncategorized] ~93-~93: “the” seems less likely than “to”.
Context: .... Visit Settings… and Developer tab the click Edit Config which will edit ...
(AI_HYDRA_LEO_CP_THE_TO)
[uncategorized] ~119-~119: Possible missing comma found.
Context: ...You can then use Claude to control Home Assistant similar to how you control Home Assista...
(AI_HYDRA_LEO_MISSING_COMMA)
[uncategorized] ~148-~148: Possible missing comma found.
Context: ...ubleshooting information for Claude for Desktop since it is the primary client. Also se...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~169-~169: You have already used ‘trying to’ in nearby sentences. Consider using one of the replacements to let your writing stand out.
Context: ...ach to MCP server Home Assistant" When trying to configure a client like Claude Desktop ...
(REP_TRY)
[typographical] ~179-~179: After the expression ‘for example’ a comma is usually used.
Context: ...rst check debug logs on the client. For example in Claude for Desktop: 1. Visit *Setti...
(COMMA_FOR_EXAMPLE)
[uncategorized] ~191-~191: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means the MCP Server integrat...
(UNLIKELY_OPENING_PUNCTUATION)
[uncategorized] ~194-~194: Loose punctuation mark.
Context: ... 'http://localhost:8123/mcp_server/sse'`: this means that the long live acce...
(UNLIKELY_OPENING_PUNCTUATION)
🪛 Markdownlint (0.37.0)
source/_integrations/mcp_server.markdown
55-55: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
88-88: Expected: 0 or 2; Actual: 1
Trailing spaces
(MD009, no-trailing-spaces)
123-123: Expected: 1; Actual: 2
Multiple consecutive blank lines
(MD012, no-multiple-blanks)
145-145: Expected: 1; Actual: 2
Multiple consecutive blank lines
(MD012, no-multiple-blanks)
|
|
||
| ## Architecture Overview | ||
|
|
||
| This integration can provide similar functionality as other LLM-ased conversation |
There was a problem hiding this comment.
Fix typo in "LLM-ased"
Correct the typo in the word "LLM-ased".
-This integration can provide similar functionality as other LLM-ased conversation
+This integration can provide similar functionality as other LLM-based conversation📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| This integration can provide similar functionality as other LLM-ased conversation | |
| This integration can provide similar functionality as other LLM-based conversation |
Proposed change
Add documentation for Model Context Protocol Server, a new core integration.
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.Summary by CodeRabbit
Summary by CodeRabbit
New Features
Documentation