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.
Trying to reach the server from a container on the same box, so stdio is out.
sdods mcp --http --port 4001AUTH_FAILED HTTP mode needs a bearer token.
→ Pass --token <secret> (dev) or set SDODS_MCP_TOKEN. Production deployments use scoped tokens
from `sdods tokens create` via the web server.Exit code 2. I did not expect auth on localhost. Is there a way to turn it off for a dev box?
Accepted answer
There is not, and that is on purpose: the moment the server speaks HTTP it is reachable by anything on the machine, including any page a browser has open. So it refuses to start without something to check.
For a dev box, one shared secret is fine:
SDODS_MCP_TOKEN=$(openssl rand -hex 32) sdods mcp --http --port 4001or --token <secret> if you would rather see it in the command. That path accepts exactly that one token and has no notion of scopes.
For anything a second person will use, do not use sdods mcp --http at all. Run the web server, which serves MCP at /mcp and checks real tokens:
sdods serve
sdods tokens create --user qa-bot --name mcp --scopes projects:read,features:read,runs:readThen the token's scopes decide which tools the client is even shown. MCP has the transport table.
Worth knowing for the container case: exit code 2 is the configuration-or-usage code, so a supervisor that restarts on non-zero will just spin. Set the variable in the unit or the compose env rather than letting it retry.
Wrap 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.