Usually when configuring MCP servers you set Streamable HTTP or SSE in the "type" parameter, e.g:
{
"mcpServers": {
"crawl4ai-sse" : {
"type": "sse",
"url" : "https://crawl4ai.my.domain/mcp/sse"
},
"crawl4ai-http" : {
"type": "streamableHttp",
"url" : "https://crawl4ai.my.domain/mcp/http"
}
}
But when providing either of these Bolt fails to save the config with the error "Invalid JSON format: The data couldn't be read because it is missing."
I'm assuming either bolt is using a different configuration parameter for the transport type or only supports local servers running in STDIO mode?
If it is the latter - I'd like to request streamable HTTP and SSE transports (although streamable HTTP will replace SSE-only mode in a future MCP specification) as the majority of MCP servers I consume these days are networked.