Skip to content

Commit fd18272

Browse files
authored
Chore(Konnect MCP): Update MCP page to remove labs mention
1 parent 401ede7 commit fd18272

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎app/_landing_pages/konnect-platform/konnect-mcp.yaml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -295,7 +295,7 @@ rows:
295295
MCP server access is enabled by default for all organizations. Organization admins can disable this from [**AI Settings**](https://cloud.konghq.com/global/organization/settings/ai-settings), after which no user will be able to access the MCP server.
296296
- q: Is any of my data sent to an LLM provider when using the MCP server?
297297
a: |
298-
If you have [KAi enabled](https://cloud.konghq.com/global/organization/labs/kai), an additional `KnowledgeBase` tool will be available via the MCP server. This tool creates embeddings from your query and uses a re-ranking model to improve documentation search results. These models are both hosted on AWS Bedrock and no training is performed on your data.
298+
If you have [KAi enabled](https://cloud.konghq.com/global/organization/settings/ai-settings), an additional `KnowledgeBase` tool will be available via the MCP server. This tool creates embeddings from your query and uses a re-ranking model to improve documentation search results. These models are both hosted on AWS Bedrock and no training is performed on your data.
299299
- q: How does user access control work for MCP tools?
300300
a: |
301301
Access to MCP tools is based on the permission levels of the user whose PAT / SPAT is used for authentication.
@@ -307,4 +307,4 @@ rows:
307307
Check your internet connection, verify the server URL is correct, and ensure your firewall isn't blocking `global.mcp.konghq.com`.
308308
- q: Tool execution is failing. How do I troubleshoot?
309309
a: |
310-
Check parameter correctness, verify you have resource access permissions, wait if you're rate limited, and confirm the resource exists.
310+
Check parameter correctness, verify you have resource access permissions, wait if you're rate limited, and confirm the resource exists.

0 commit comments

Comments
 (0)