Troubleshoot SnapCode

Resolve common issues with SnapCode installation, startup, and pipeline execution.

MCP servers not connected

Symptom Cause Resolution
/mcp shows No MCP servers configured Credentials are missing from the shell environment or the terminal was not restarted after setting them.
  1. Verify the environment variables are visible to the current terminal. The following example checks SNAPLOGIC_BASE_URL:

    macOS / Linux:

    echo $SNAPLOGIC_BASE_URL

    Windows (PowerShell):

    $env:SNAPLOGIC_BASE_URL
    If the command prints your SnapLogic environment URL, the variable is visible to the current shell. If it returns an empty value, the terminal has not picked up the new values yet — open a new terminal and try again. Refer to Set your SnapLogic credentials.
  2. Run /doctor inside Claude Code for MCP diagnostics, including missing environment variables.
plugin:snapcode:snaplogic is connected but tools return a 401 error SnapLogic credentials are missing or incorrect in the shell environment.
  1. Verify that SNAPLOGIC_API_USER and SNAPLOGIC_API_PASS are set correctly in your shell environment.
  2. Confirm you can log in to your SnapLogic control plane with those credentials.
  3. Open a new terminal and restart Claude Code so the updated values take effect.

Skill not recognized

Symptom Cause Resolution
SnapCode skill is not available when you start Claude Code You are not running claude from the SnapCode directory, or the global install has not been run
  • Run claude from inside the SnapCode directory.
  • Or install the plugin, which makes SnapCode available from any directory. See Install SnapCode.

Pipeline validation and execution errors

Symptom Cause Resolution
Validation fails after deploy with a snap or field error A snap parameter is missing, incorrectly typed, or references a field that does not exist Tell SnapCode what the error means and what the correct value should be. For example: 
Fix it — subtotal should be qty × unit_price
SnapCode edits the .py file, retranslates, redeploys, and revalidates automatically.
Pipeline passes local execution but fails Platform validation or execution Difference in behavior between the local execution engine and the SnapLogic Platform This is a non-conformance between the local engine and the Platform. Report it to the SnapCode team with the pipeline file and the exact error so it can be investigated.