What problem does it solve?
Provides an automated, repeatable workflow to fully verify MCP server behavior and all MCP tools against a real dbt project so code changes do not introduce regressions or incorrect tool outputs.
Core Features & Use Cases
- Generates a temporary end-to-end test script tailored to a given dbt project and executes checks for all eight MCP tools to ensure non-empty, valid outputs.
- Validates both full-mode and single-environment behaviors, including presence or absence of specific warning fields and preset checks loaded from configuration.
- Use cases include verifying changes to the MCP server implementation before merging pull requests, reproducing single-env vs full-mode differences, and diagnosing empty or unexpected tool responses.
Quick Start
Run the recce-mcp-e2e skill with a dbt project path to generate and execute a temporary MCP E2E test script that reports pass or fail for all checks.