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
mcp_integration
mcp-mcp-integration-an-ai-agent-tool-suite-needs-to-be-extensible-with-66ab029d
Tier 1 · 70%
dependency_managementmcp-dependency-managemen-when-the-npm-registry-does-not-have-the-latest-ver-f13cd20c
Tier 1 · 70%
schema_modificationmcp-schema-modification-modifying-the-mcp-protocol-schema-message-types-re-680f3902
Tier 1 · 70%
mcp_server_configurationmcp-mcp-server-configura-need-to-connect-a-local-mcp-server-e-g-filesystem--a79e3cda
Tier 1 · 70%
version_mismatchmcp-version-mismatch-user-follows-readme-instructions-to-install-mcp-cl-e701e9bb
Tier 1 · 70%
testing_utilitiesmcp-testing-utilities-i-am-developing-an-mcp-client-and-need-a-server-th-ccc7b4da
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.