Module resolution issues with TypeScript ESM imports

[enkhbold470]

We're experiencing issues with TypeScript module resolution when trying to import the MCP SDK in an ESM project. We've tried several approaches:

1. Direct imports:

import { Server } from "@modelcontextprotocol/sdk/server";
import { Function, FunctionParameter } from "@modelcontextprotocol/sdk/server/mcp";

2. Full path imports:

import { Server } from "@modelcontextprotocol/sdk/dist/esm/server/index.js";
import { Function, FunctionParameter } from "@modelcontextprotocol/sdk/dist/esm/server/mcp.js";

Both approaches result in TypeScript errors:

Cannot find module '@modelcontextprotocol/sdk/server' or its corresponding type declarations.
Cannot find module '@modelcontextprotocol/sdk/server/mcp' or its corresponding type declarations.

Our project configuration:

// package.json
{
  "type": "module",
  "dependencies": {
    "@modelcontextprotocol/sdk": "latest"
  }
}

// tsconfig.json
{
  "compilerOptions": {
    "target": "ES2020",
    "module": "ESNext",
    "moduleResolution": "bundler",
    // ...
  }
}

Could you please provide guidance on the correct way to import the SDK in an ESM TypeScript project?

[Pdash-exceeds]

@enkhbold470 - check this patch #217

[ipenywis]

This is still an issue with latest version 1.9.0.

[https-eduardo]

This is still an issue with latest version 1.9.0.

Changing from:
import { ResourceTemplate } from "@modelcontextprotocol/sdk/server/mcp";
To:
import { ResourceTemplate } from "@modelcontextprotocol/sdk/server/mcp.js";

Solved for me