I assumed an npm package name was mine. It wasn't.

· Workflow

Quick heads up if you’re using my GSC MCP server.

When I wrote the install guide, I told everyone to run npx -y gsc-mcp-server in their Claude Desktop config. I assumed that npm name was mine. It wasn’t. It belongs to another developer (Sofian Bettayeb) who published a different GSC MCP under the same name in January.

So every reader following my guide was downloading his package, not mine. 7 tools instead of my 20. Different auth. Different everything.

My mistake. Should have run npm view gsc-mcp-server before publishing the post. Ten second command I skipped.

Fixed now. My actual code is on npm as suganthan-gsc-mcp.

If you set this up from my blog, change your Claude Desktop config from:

"args": ["-y", "gsc-mcp-server"]

to:

"args": ["-y", "suganthan-gsc-mcp"]

Restart Claude Desktop and you’ll get the actual 20 tools with OAuth refresh, multi-site, content decay, cannibalisation, and the rest.

The updated blog post has the full install guide and a changelog entry explaining what happened.