Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Registered the server the way the guide says:
claude mcp add sdods -- npx sdods mcp --project demo-shop --env stagingclaude mcp list shows sdods. But when I ask it to list projects it says it has no such tool and starts reading files instead. No error anywhere. Where do I even look?
Accepted answer
claude mcp list only proves the entry is in the config. It does not prove the server started. Run it by hand first:
sdods mcp --project demo-shop --env staging --list-toolsThat prints the catalogue and exits. If it prints, the server is fine and the client is the problem; if it throws, you get the real error instead of a silent client.
The usual real error is that the project or env does not resolve from the directory the client launched npx in. sdods mcp is started with the client's cwd, not yours.
Second thing to check: --caps. The default is core,analyze,run,data,schedules. If the tool you were expecting is an agent or issue tool it is genuinely not there:
sdods mcp --project demo-shop --caps all --list-toolsAdding one failure mode to Kostya's answer, because it bites people once and never again.
stdio MCP is a protocol on stdout. Anything else written there corrupts the stream and the client drops the server without a message. If you have a shell profile that prints a banner, or an npx that logs an install line on first use, that is enough.
Pre-install so npx has nothing to say, then re-add:
npm i -g sdods
claude mcp remove sdods
claude mcp add sdods -- sdods mcp --project demo-shop --env stagingWrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.