MCP plugin: ESM support

[karlismelderis-mckinsey]

What version of kubb is running?

4.26.0

What kind of platform do you use?

None

Your kubb.config.ts config file?

generated server.ts is failing import resolution when I chose to keep `.ts` extensions and utilise node ability to run TS as is 

`.js` extensions are missing for MCP and stdio imports


import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';


would be great to support this setup so I don't need to build MCP server and run the code as is

Swagger/OpenAPI file?

What version of external packages are you using(@tanstack-query, MSW, React, Vue, ...)

What steps can reproduce the bug?

generate code and run it with node instead of tsx

How often does this bug happen?

None

What is the expected behavior?

No response

Additional information

No response

[karlismelderis-mckinsey]

I did a quick check of https://github.com/modelcontextprotocol/typescript-sdk and it seems that with v2 library that's currently in main this issue will be resolved on their side 🤔

[dosubot]

This is a confirmed gap in the MCP plugin. The imports for the MCP SDK are generated without .js extensions:

<File.Import name={['McpServer']} path={'@modelcontextprotocol/sdk/server/mcp'} />
<File.Import name={['StdioServerTransport']} path={'@modelcontextprotocol/sdk/server/stdio'} />

There's currently no configuration option in the MCP plugin's types to control import extensions or enable ESM mode. The fix would need to update these paths to include .js extensions for Node's ESM resolution.

Written by @dosu, approved by stijnvanhulle

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.

[stijnvanhulle]

@karlismelderis-mckinsey we also have other issues with typecheck taking minutes so would be nice to see improvements in v2

[stijnvanhulle]

@karlismelderis-mckinsey I will close this one as we don't have control over @modelcontextprotocol/sdk is being handeld/published