modelcontextprotocol / modelcontextprotocol/servers

Can't start sequential-thinking MCP with cursor

Open
#2,421 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug waiting for submitter
Dominant language
TypeScript
Stars
90.5k
Forks
11.7k
Avg merge
2d 2h
Merged PRs (30d)
5

Description

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Install MCP on cursor mcp.json
"sequential-thinking": {
        "command": "npx",
        "args": [
          "-y",
          "@modelcontextprotocol/server-sequential-thinking"
        ]
      }

Cursor logs:

2025-07-24 13:22:30.407 [info] user-sequential-thinking: Starting new stdio process with command: npx -y @modelcontextprotocol/server-sequential-thinking
2025-07-24 13:22:31.779 [error] user-sequential-thinking: node:internal/modules/esm/resolve:274
    throw new ERR_MODULE_NOT_FOUND(
          ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/USER/.npm/_npx/de2bd410102f5eda/node_modules/zod/index.js' imported from /Users/USER/.npm/_npx/de2bd410102f5eda/node_modules/@modelcontextprotocol/sdk/dist/types.js
    at finalizeResolution (node:internal/modules/esm/resolve:274:11)
    at moduleResolve (node:internal/modules/esm/resolve:859:10)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:801:12)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:725:25)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:309:38)
    at #link (node:internal/modules/esm/module_job:208:49) {
  code: 'ERR_MODULE_NOT_FOUND',
  url: 'file:///Users/USER/.npm/_npx/de2bd410102f5eda/node_modules/zod/index.js'
}

Node.js v24.4.1

2025-07-24 13:22:31.785 [info] user-sequential-thinking: Client closed for command

When checking the missing files, there's only index.d.ts file in the directory.

$ ls /Users/USER/.npm/_npx/de2bd410102f5eda/node_modules/zod/
index.d.ts package.json README.md src v3 v4

$ npm list @modelcontextprotocol/sdk
├── @modelcontextprotocol/sdk@1.17.0
└─┬ @modelcontextprotocol/server-sequential-thinking@2025.7.1
└── @modelcontextprotocol/sdk@0.5.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with the Cursor mcp.json command, npx -y @modelcontextprotocol/server-sequential-thinking, and Node.js 24.4.1. Inspect the installed @modelcontextprotocol/sdk, @modelcontextprotocol/server-sequential-thinking, and zod package contents shown in the report, then compare them with the npm list dependency versions. Done means the sequential-thinking server starts from Cursor without the missing zod/index.js error.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, typescript
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.