Module '"@mcp-ui/server"' has no exported member 'createUIResource'.

[kdawgwilk]

I think some of the wires are crossed with the import paths somehow. I see this error with:

• NodeJS: 22
• TS: ~5.8.3
• @mcp-ui/server: ^5.11.0
• package.json: "type": "module",
• tsconfig.json

{
  "compilerOptions": {
    "lib": ["es2024", "ESNext.Array", "ESNext.Collection", "ESNext.Iterator"],
    "module": "NodeNext",
    "esModuleInterop": true,
    "moduleResolution": "node16",
    "noImplicitReturns": true,
    "noUnusedLocals": true,
    "outDir": "lib",
    "sourceMap": true,
    "strict": true,
    "target": "es2022",
    "skipLibCheck": true,
    "baseUrl": ".",
    "paths": {
      "@/*": ["./src/*"]
    }
  },
  "compileOnSave": true,
  "include": ["src"]
}

[kdawgwilk]

OpenAI Codex found this:

Why the import failed

• TypeScript error: src/contexts/mcps/ui.mcp.ts:6 imports createUIResource from @mcp-ui/server, but TS reported it isn’t exported.
• The package is installed and does export it. See node_modules/@mcp-ui/server/dist/src/index.d.ts which declares export declare function createUIResource(...).
• Root cause: tsconfig used module: NodeNext + moduleResolution: node16. Under this resolution, TypeScript requires explicit file extensions in ESM re-exports. The
  package’s dist/index.d.ts does export * from './src/index' (no extension), which Node16 resolution doesn’t follow.
• From a tsc trace: it resolved @mcp-ui/server to .../dist/index.d.ts, then tried ./src/index and skipped because it didn’t find a directory; it didn’t follow to ./src/ index.d.ts, so the named exports never surfaced to the compiler.

So it looks like the build output is missing the .js file extensions

[kdawgwilk]

This patch-package diff fixed it for me

diff --git a/node_modules/@mcp-ui/server/dist/index.d.ts b/node_modules/@mcp-ui/server/dist/index.d.ts
index 1111111..2222222 100644
--- a/node_modules/@mcp-ui/server/dist/index.d.ts
+++ b/node_modules/@mcp-ui/server/dist/index.d.ts
@@
-export * from './src/index'
+export * from './src/index.js'

[tylerslaton]

Hey @kdawgwilk - did you find any way around this? Ah, misread - your solution works a treat for now until this is fixed. Thanks!

[idosal]

Thanks for reporting @kdawgwilk ! This should be solved in the latest version.