val server= config.mcpServers["http-server"]!!

assertNull(server.command)

assertEquals("http://localhost:8080/mcp", server.url)

assertNull(server.sseUrl)

assertEquals(emptyList(), server.args)

}

@Test

funshould_parse_config_with_sse_url_only() {

val configJson="""

""".trimIndent()

val config=McpServer.tryParse(configJson)

assertNotNull(config)

assertEquals(1, config.mcpServers.size)

val server= config.mcpServers["sse-server"]!!

assertNull(server.command)

assertNull(server.url)

assertEquals("http://localhost:8080/sse", server.sseUrl)

assertEquals(emptyList(), server.args)

}

@Test

funshould_parse_config_with_both_command_and_url() {

val server= config.mcpServers["mixed-server"]!!

assertEquals("npx", server.command)

assertEquals("http://localhost:8080/mcp", server.url)

assertNull(server.sseUrl)

assertEquals(listOf("@modelcontextprotocol/server-stdio"), server.args)

}

@Test

funshould_parse_config_with_all_transport_types() {

val configJson="""

""".trimIndent()

val config=McpServer.tryParse(configJson)

assertNotNull(config)

assertEquals(1, config.mcpServers.size)

val server= config.mcpServers["all-transports-server"]!!

assertEquals("npx", server.command)

assertEquals("http://localhost:8080/mcp", server.url)

assertEquals("http://localhost:8080/sse", server.sseUrl)

assertEquals(listOf("@modelcontextprotocol/server-stdio"), server.args)

}

@Test

funshould_parse_config_with_all_optional_fields() {

AutoDev now supports MCP (Model Context Protocol) servers viamultiple transport protocols, thanks to the upgrade to kotlin-sdk 0.6.0.

AutoDev now supports MCP (Model Context Protocol) servers viaHTTP transport, thanks to the upgrade to kotlin-sdk 0.6.0.

MCP servers can be configured in your`mcp_server.json` file usingany of these transport types:

MCP servers can be configured in your`mcp_server.json` file usingeither of these transport types:

1.**Command-based (stdio)** - for local MCP servers

2.**URL-based (HTTP)** - for remote MCP servers with HTTP transport

3.**SSE URL-based (Server-Sent Events)** - for remote MCP servers with SSE transport

}

{

"mcpServers": {

"sse-server": {

"sseUrl":"http://localhost:8080/sse",

"args": []

}

}

}

You can useall transport types in the same configuration:

You can useboth transport types in the same configuration:

{

"args": [],

"autoApprove": ["safe_tool"],

"requiresConfirmation": ["dangerous_tool"]

},

"remote-sse-api": {

"sseUrl":"https://api.example.com/mcp/sse?session=123",

"args": [],

"autoApprove": ["read_only_tool"]

}

}

}

-**At least one**of`command`,`url`,or`sseUrl` must be specified

-`args`: Array of arguments (can be empty for HTTP/SSE servers)

-**Either**`command`or`url` must be specified

-`args`: Array of arguments (can be empty for HTTP servers)

AutoDev automatically selects the appropriate transport based on your configuration (in priority order):

AutoDev automatically selects the appropriate transport based on your configuration:

1. If`sseUrl` is provided → Uses`SseClientTransport` (highest priority)

2. If`url` is provided → Uses`StreamableHttpClientTransport`

3. If`command` is provided → Uses`StdioClientTransport`

4. If none are provided → Logs warning and skips the server

1. If`url` is provided → Uses`StreamableHttpClientTransport`

2. If`command` is provided → Uses`StdioClientTransport`

3. If neither is provided → Logs warning and skips the server

**Note**: Ifmultiple transport options are specified,SSE hasthe highestpriority, followed by HTTP, then stdio.

**Note**: Ifboth transport options are specified,HTTP has priority over stdio.

-**Remote Access**: Connect to MCP servers running on different machines

-**Scalability**: Better for production deployments

-**Firewall Friendly**: Uses standard HTTP protocols

-**Load Balancing**: Can be used with load balancers and reverse proxies

-**Real-time Communication**: Server-Sent Events provide efficient streaming

-**Low Latency**: Optimized for real-time data streaming

-**Browser Compatible**: Standard web technology

-**Connection Persistence**: Maintains long-lived connections for better performance

Existing configurations with`command` will continue to work unchanged. To migrate a server to remote transports:

}

**After (SSE):**

{

"my-server": {

"sseUrl":"http://localhost:3000/sse",

"args": []

}

}

- Verify the HTTP/SSE server is running and accessible

- Verify the HTTP server is running and accessible

- Check firewall settings for HTTP connections

- Ensure the MCP server supports the appropriate transport protocol (HTTP or SSE)

- For SSE: Verify the server supports Server-Sent Events and the endpoint is correct

- Ensure the MCP server supports the HTTP transport protocol

- Validate JSON syntax in your configuration file

- Ensureat least one of`command`,`url`,or`sseUrl` is specified for each server

- Ensureeither`command`or`url` is specified for each server

- Check server logs for detailed error messages

See`example/mcp/streamable-http-example.mcp.json` for a complete configuration example withall transport types (stdio, HTTP,andSSE).

See`example/mcp/streamable-http-example.mcp.json` for a complete configuration example withboth transport types (stdioandHTTP).

"url":"http://localhost:8080/mcp",

"args": []

},

"remote-sse-server": {

"sseUrl":"http://localhost:8080/sse",

"args": []

},

"stdio-server": {

"command":"npx",

"args": ["@modelcontextprotocol/server-stdio"]

"disabled":false,

"autoApprove": ["safe_tool"],

"requiresConfirmation": ["dangerous_tool"]

},

"sse-with-query-params": {

"sseUrl":"https://api.example.com/mcp/sse?session=123&token=abc",

"args": [],

"autoApprove": ["read_only_tool"]

}

}

}