Quick status: the errors such as mcp.server.fastmcp import errors, McpError import errors, tool_use/tool_result mismatches were due to a breaking update released by MCP on 2026-07-28, which changed parts of the SDK the course was originally built in 2025. This isn’t something on your end — the environment genuinely needs a few extra steps beyond what’s shown in the videos to keep working with today’s package versions.
We’ve pushed markdown notes to L3, L4, L6, and L7 with the exact commands needed to get things running again. Please check those notebooks for the updated instructions.
Appreciate your patience! Feel free to keep sharing anything unexpected, it helps us prioritize.
Lesly - DLAI
2 Likes
L3 issue: inspector not found (and node+npm version outdated) Nov. 2026
(mcp_project) jovyan@ip-172-29-19-203:~/work/L4/mcp_project$ npx @modelcontextprotocol/inspector uv run research_server.py
Need to install the following packages:
@modelcontextprotocol/inspector
Ok to proceed? (y) y
sh: 1: inspector: not found
npm notice New major version of npm available! 7.24.0 → 12.2.1
npm notice Changelog: Release v12.2.1 · npm/cli · GitHub
npm notice Run npm install -g npm@12.2.1 to update!
npm notice
(mcp_project) jovyan@ip-172-29-19-203:~/work/L4/mcp_project$ npm install -g npm@12.2.1
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: npm@12.2.1
npm ERR! notsup Required: {“node”:“^22.22.2 || ^24.15.0 || >=26.0.0”}
npm ERR! notsup Actual: {“npm”:“7.24.0”,“node”:“v18.19.0”}
1 Like
Thank you for reporting. We’re updating different notebooks due to model updates.
We’ll keep you updated!