recce-mcp-e2e

Verify all MCP server tools against a real dbt project.

470|26|Updated Oct 6, 2023
One-click install
npx skills add https://github.com/DataRecce/recce --skill recce-mcp-e2e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recce-mcp-e2e
Source: https://github.com/DataRecce/recce/tree/main/.claude/skills/recce-mcp-e2e
Command: npx skills add https://github.com/DataRecce/recce --skill recce-mcp-e2e

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about recce-mcp-e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify MCP server tools end-to-end against a dbt project?

To verify MCP server tools end-to-end against a dbt project, you can generate and execute a temporary test script that checks all eight MCP tools for non-empty, valid outputs. This validates both full-mode and single-environment behaviors.

What is needed to run e2e testing for dbt MCP handlers?

E2e testing for dbt MCP handlers requires a dbt project directory containing target/manifest.json and target-base/manifest.json. You also need permission to write and execute a temporary test script, plus the ability to locate the recce repository root to adjust PYTHONPATH.

When should I validate MCP server behavior against a dbt project?

Validate MCP server behavior against a dbt project when recce/mcp_server.py, MCP handlers, single-env logic, or error classification are modified. It is specifically used for validating before merging MCP-related pull requests to prevent regressions.

Can I use this approach to reproduce single-env vs full-mode differences in dbt?

Yes, you can reproduce single-env vs full-mode differences by running an e2e test script that validates the presence or absence of specific warning fields and preset checks loaded from configuration. This helps diagnose empty or unexpected tool responses.

Does dbt MCP e2e testing require specific manifest files?

Yes, dbt MCP e2e testing requires a dbt project directory containing both target/manifest.json and target-base/manifest.json. These manifests are essential for the test script to accurately compare and validate the server's tool outputs.