Sign in to run requests with your own sandbox key. Sign in

Install

Add Cascades to Claude Desktop

  1. Open Claude Desktop → Settings → Developer → Edit Config. That opens claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\).
  2. Merge the JSON below into the file (keep any other servers you already have).
  3. Quit and reopen Claude Desktop. The hammer icon lists the nine cascades_* tools.
Your docs key stops working after 1 hour
When you are signed in, the commands and configs on this page fill in your docs key, which expires 1 hour after it is created or when you sign out. After that, the Cascades tools in Claude Desktop stop working. For a key that lasts 90 days, create one on the API keys page. Then replace the CASCADES_API_KEY value of the cascades server in Claude Desktop's MCP config with the new key.
claude_desktop_config.json
{
  "mcpServers": {
    "cascades": {
      "command": "npx",
      "args": [
        "-y",
        "@crscreditapi/cascades-mcp-server"
      ],
      "env": {
        "CASCADES_API_KEY": "{{API_KEY}}",
        "CASCADES_PROD_BASE_URL": "https://cascades.crscreditapi.com"
      }
    }
  }
}

Notes

  • CASCADES_PROD_BASE_URL is the host without /api/v1 (https://cascades.crscreditapi.com); the server adds the prefix.
  • The key needs workflows:read, workflows:write, executions:read, executions:write. A key missing a scope gets 403 insufficient_scope on the affected tool only.
  • Sandbox keys can only run in test mode: execution_mode: "live" is billable, needs a production-approved account, and is rejected for docs-issued keys.
  • Claude Desktop launches the server with its own PATH; if npx is not found, replace "command": "npx" with the absolute path from which npx.

Test with MCP Inspector

Check the key and host before trusting the editor integration: this runs the server with the same environment and lets you call each tool from a browser UI.

Your docs key stops working after 1 hour
When you are signed in, the commands and configs on this page fill in your docs key, which expires 1 hour after it is created or when you sign out. After that, the Cascades tools in Claude Desktop stop working. For a key that lasts 90 days, create one on the API keys page. Then replace the CASCADES_API_KEY value of the cascades server in Claude Desktop's MCP config with the new key.
Terminal
CASCADES_API_KEY={{API_KEY}} CASCADES_PROD_BASE_URL=https://cascades.crscreditapi.com \
  npx @modelcontextprotocol/inspector npx -y @crscreditapi/cascades-mcp-server

What you get

Tool What it does Access REST call
cascades_create_workflow Create a new cascade (decision workflow) from a JSON definition, owned by the API key's account. write POST /workflows
cascades_delete_workflow Delete a cascade (soft-delete). destructive DELETE /workflows/{id}
cascades_generate_workflow Build a cascade from a plain-English policy description using the Cascades AI builder, then create it (by default) so it is immediately runnable with cascades_trigger_workflow. write POST /workflows/generate
cascades_get_execution Fetch a single cascade execution by id to check its status and results. read GET /executions/{id}
cascades_get_workflow Fetch one cascade by id, including its full node graph (`definition`). read GET /workflows/{id}
cascades_list_test_cases List the pre-registered sandbox test-case subjects for a cascade — the synthetic applicants the CRS Testcase Service has authored for that cascade's products (e.g. specific credit-score bands). read GET /workflows/{id}/test_cases
cascades_list_workflows List the caller's saved Cascades (decision workflows) — their id, code, name, use_case, trigger_type, and whether each is active. read GET /workflows
cascades_trigger_workflow Run a saved cascade for an applicant — i.e. start a decision. write POST /workflows/{id}/trigger
cascades_update_workflow Update an existing cascade. write PATCH /workflows/{id}