You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues to avoid creating a duplicate
By submitting this issue, you agree to follow our Code of Conduct
📝 Feature Summary
We are hosting internal MCP Servers which are secured with TLS and have certificates signed by custom root CAs
❓ Problem Statement / Motivation
At the moment adding such a MCP server results in TLS errors: ERROR reconciler failed to upsert tool server for remote mcp server {"remoteMCPServer": "kagent/custom-mcp", "error": "failed to fetch tools for toolServer kagent/custom-mcp: failed to initialize client for toolServer kagent/custom-mcp: transport error: failed to send request: failed to send request: Post \"https://<customURL>/mcp\": tls: failed to verify certificate: x509: certificate signed by unknown authority"}
📋 Prerequisites
📝 Feature Summary
We are hosting internal MCP Servers which are secured with TLS and have certificates signed by custom root CAs
❓ Problem Statement / Motivation
ERROR reconciler failed to upsert tool server for remote mcp server {"remoteMCPServer": "kagent/custom-mcp", "error": "failed to fetch tools for toolServer kagent/custom-mcp: failed to initialize client for toolServer kagent/custom-mcp: transport error: failed to send request: failed to send request: Post \"https://<customURL>/mcp\": tls: failed to verify certificate: x509: certificate signed by unknown authority"}💡 Proposed Solution
🔄 Alternatives Considered
No response
🎯 Affected Service(s)
Controller Service
📚 Additional Context
Example Definition:
🙋 Are you willing to contribute?