Cursor MCP "Failed to create client" with @upstash/context7-mcp using npx: fix

Question

A user configured the context7 MCP server in Cursor with npx and the args "-y", "@upstash/context7-mcp", but Cursor shows "Failed to create client." Running the npx command with the @latest tag in a terminal printed "'context7-mcp' is not recognized as an internal or external command, operable program or batch file." How can the server be started?

Originally asked on GitHub: https://github.com/upstash/context7/issues/66

AgentArmorHQ team · Accepted Answer

Status: fixed. Several users reported that removing the `@latest` tag from the npx arguments made the Cursor MCP client connect, and the issue was closed as completed.

Use this config:

```json
{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp"]
    }
  }
}
```

One user reported the error disappeared after clicking the refresh button in Cursor's MCP panel, without other changes. Another user confirmed that the config worked after removing `@latest`.

A maintainer asked users to run `npm view @upstash/context7-mcp bin`. The expected output is `{ 'context7-mcp': 'dist/index.js' }`. One reporter on Node v22.9.0 and npm 11.3.0 posted that output in the thread, but the thread does not draw a conclusion from it.

A maintainer also suggested trying `bunx` or `deno` in place of npx. The thread does not confirm whether those worked.

General advice: after changing the config, use Cursor's MCP refresh button or restart Cursor so the configuration is reloaded.

AgentArmorHQ team · Answer

**What @vietquang99 tried on GitHub** (Didn't work)

Ran `npx -y @upstash/context7-mcp@latest` directly in the terminal; it returned "'context7-mcp' is not recognized as an internal or external command, operable program or batch file."

Source: https://github.com/upstash/context7/issues/66

AgentArmorHQ team · Answer

**What @kuzniets tried on GitHub** (Worked)

Removed the `@latest` tag from the npx args so the config used just `@upstash/context7-mcp`; it worked.

Source: https://github.com/upstash/context7/issues/66#issuecomment-2824572829

AgentArmorHQ team · Answer

**What @Umakantamaharana tried on GitHub** (Worked)

Clicked the refresh button in Cursor's MCP panel; the error disappeared.

Source: https://github.com/upstash/context7/issues/66#issuecomment-2823222500

AgentArmorHQ team · Answer

**What @antonioc-cl tried on GitHub** (Outcome unclear)

Ran `npm view @upstash/context7-mcp bin`, which output `{ 'context7-mcp': 'dist/index.js' }`, on Node v22.9.0 and npm 11.3.0. The Cursor log showed "No server info found".

Source: https://github.com/upstash/context7/issues/66#issuecomment-2822562164

AgentArmorHQ team · Answer

**What @enesgules tried on GitHub** (Outcome unclear)

Maintainer asked the reporter to run `npm view @upstash/context7-mcp bin` to check the package binary, and asked for the npm version.

Source: https://github.com/upstash/context7/issues/66#issuecomment-2822318051

Cursor MCP "Failed to create client" with @upstash/context7-mcp using npx: fix

6 answers

Add your answer or comment

Cursor MCP "Failed to create client" with @upstash/context7-mcp using npx: fix

6 answers

Add your answer or comment

Related questions