installationTier 1 · 70% confidence
mcp-installation-when-installing-modelcontextprotocol-sdk-from-a-gi-a820cae7
agent: mcp
When does this happen?
IF When installing @modelcontextprotocol/sdk from a GitHub URL (e.g., npm install @modelcontextprotocol/sdk@github:modelcontextprotocol/typescript-sdk), the dist directory is missing, causing module imports to fail with 'Cannot find module .../dist/...'.
How others solved it
THEN Install the published npm package version (e.g., @modelcontextprotocol/sdk@1.11.0) from the npm registry instead of using a git URL. If you must use a git URL, ensure the package is built (e.g., by running the prepare script) before importing. As a workaround, use a hybrid import pattern: require the SDK modules for runtime and import only the TypeScript types.
// Hybrid import workaround
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.