Troubleshooting Coder Setup
These checks are for Coder 0.6.32, not every MemStrata product. Use Conversational setup for its separate services.
Local service will not start
Section titled “Local service will not start”Run memstrata-coder status and memstrata-coder doctor. Distinguish the API/MCP service on port 8000 from the provider harness on port 8080.
For the harness, curl http://127.0.0.1:8080/ should return a response such as {"status":"alive","version":"0.6.32"}. The old /health and 5.2.x examples are not this release’s contract.
Check which process owns a conflicting port before acting. Do not stop an unrelated process. If you deliberately choose another harness port, use memstrata-coder start --port 8181 and update the client routing accordingly; changing the harness port does not move the MCP service.
MCP tools do not appear
Section titled “MCP tools do not appear”Use the HTTP MCP URL http://127.0.0.1:8000/mcp/ and your host’s connection log and tool discovery. Do not point MCP at the provider harness. See custom MCP setup.
Host permission, reload and tool-selection behavior varies by client version. A client must actually call a Coder tool; not every prompt or inline completion is captured automatically.
Project is missing or context is empty
Section titled “Project is missing or context is empty”Run memstrata-coder project list --json. Check the project path and indexing state. A project_required response needs an explicit project selection; not_indexed needs indexing to finish.
Do not run an undocumented rebuild, clear the database or delete user data to fix a connection problem.
Savings are zero
Section titled “Savings are zero”Check whether an eligible turn was actually routed or a context pack delivered. Direct provider traffic does not appear merely because MCP is connected. Counterfactual eligibility and provider costs also matter. See Telemetry and savings; no fixed number of turns guarantees a saving.
Licensing is unreachable
Section titled “Licensing is unreachable”Check the installed product’s status and the service information. Paid features may pause after the product’s displayed offline grace period. Reinstallation does not restart a trial.
If corporate networking blocks access, ask your administrator about the documented destination and certificate chain. Do not disable TLS verification.
Windows or macOS blocks an installer
Section titled “Windows or macOS blocks an installer”Do not bypass SmartScreen, remove quarantine attributes or disable Gatekeeper on the strength of a website instruction. Use the exact artifact from the install selector, verify its published hash and publisher, and contact support if the platform still rejects it. Package signatures and Store availability vary by artifact; an old MSI/DMG example is not proof that your file is signed or notarized.
Support
Section titled “Support”Run memstrata-coder logs --lines 50 only when needed. Review and redact the output before sending it to support@memstrata.dev. Include the product, version, OS and exact error. Never send credentials, raw private code, prompts or unrelated personal files.