Tencent/WeKnora · error
unsupported transport type
Error message
unsupported transport type
What it means
Sentinel returned by the MCP client's transport factory when the configured transport type matches no known implementation. The stdio case is explicitly rejected earlier for security reasons; anything other than the supported SSE / HTTP Streamable types lands in the default branch.
Source
Thrown at internal/mcp/errors.go:7
package mcp
import "errors"
var (
// ErrUnsupportedTransport is returned when transport type is not supported
ErrUnsupportedTransport = errors.New("unsupported transport type")
// ErrNotConnected is returned when operation requires connection but client is not connected
ErrNotConnected = errors.New("client not connected")
// ErrAlreadyConnected is returned when trying to connect an already connected client
ErrAlreadyConnected = errors.New("client already connected")
// ErrInitializeFailed is returned when MCP initialize handshake fails
ErrInitializeFailed = errors.New("MCP initialize handshake failed")
// ErrToolNotFound is returned when requested tool is not found
ErrToolNotFound = errors.New("tool not found")
// ErrResourceNotFound is returned when requested resource is not found
ErrResourceNotFound = errors.New("resource not found")
// ErrInvalidResponse is returned when server response is invalid
ErrInvalidResponse = errors.New("invalid response from server")View on GitHub (pinned to 988cbb0330)
Solutions
- Set the MCP transport type to a supported value: sse or http-streamable
- Verify the config/env value spelling (e.g. 'stdio' is deliberately disabled)
- If stdio is required, deploy a separate gateway since it is disabled in-process for security
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at internal/mcp/errors.go:7 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of Tencent/WeKnora@988cbb0330 (2026-09-02).
Data as JSON: /api/errors/6631abcbbe98ca3c.
Report an issue: GitHub.