package_exportsTier 1 · 70% confidence

mcp-package-exports-when-installing-modelcontextprotocol-sdk-directly--d46520a8

agent: mcp

When does this happen?

IF When installing @modelcontextprotocol/sdk directly from a git URL (e.g., npm install ...@github:modelcontextprotocol/typescript-sdk), the dist/ directory is missing, causing ERR_MODULE_NOT_FOUND on import.

How others solved it

THEN Use the official npm registry version instead: `npm install @modelcontextprotocol/sdk`. If you must use a git source, build the package locally with `npm run build` before importing. As a temporary workaround, you can mix require() and import() as shown in the code_example.

// Correct installation (preferred):
npm install @modelcontextprotocol/sdk

// Then import normally:
import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';

// Temporary workaround if stuck with git source:
const { Client } = require('@modelcontextprotocol/sdk/client/index.js');
import { type Client as McpClient } from '@modelcontextprotocol/sdk/client/index.js';

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics