Missing dependency: @modelcontextprotocol/ext-apps not declared in package.json (breaks npx install, v0.7.6+)

[NewmanCharlz]

Description

Starting in v0.7.6 (through the current latest, v0.7.8), dist/server.js imports @modelcontextprotocol/ext-apps:

import{RESOURCE_MIME_TYPE as ee}from"@modelcontextprotocol/ext-apps/server"

but this package is not listed in package.json’s dependencies (only @azure/msal-node, @modelcontextprotocol/sdk, jose, and zod are declared). A plain npm install / npx -y mcp-dataverse never installs @modelcontextprotocol/ext-apps, so the server crashes on startup.

Reproduction

npx -y mcp-dataverse

Crashes immediately on the first initialize request with:

node:internal/modules/package_json_reader:301
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^
Error [ERR_MODULE_NOT_FOUND]: Cannot find package ‘@modelcontextprotocol/ext-apps’ imported from .../node_modules/mcp-dataverse/dist/server.js

Confirmed scope

• v0.7.5 — clean, no ext-apps import, works fine.
• v0.7.6 — bug introduced (import present, dependency missing from package.json).
• v0.7.7 — same bug.
• v0.7.8 (latest) — same bug.

Checked by downloading each version’s tarball via npm pack and grepping the compiled dist/*.js for ext-apps.

@modelcontextprotocol/ext-apps does exist on npm (currently v1.7.5), so this looks like a simple oversight — used in source but never added to package.json.

Environment

• Node.js v24.16.0, Windows
• Run via npx -y mcp-dataverse as a Claude Desktop MCP server

Workaround

Pinning to mcp-dataverse@0.7.5 avoids the crash until this is fixed.