recce-mcp-e2e

To verify MCP server changes against a real dbt project, execute an end-to-end verification workflow that validates modified server code, tool handlers, and single-env logic to ensure integration fidelity before merging.

End-to-end MCP verification is a validation process that tests MCP server modifications against a live dbt project. You need it when preparing MCP-related PRs or modifying server code and tool handlers to ensure deployment reliability.

Run end-to-end tests for dbt project workflows by invoking the packaged MCP verification workflow against your target project, utilizing the provided support pack and troubleshooting notes to validate changes before handoff.

Yes, MCP verification workflows support testing modified tool handlers. The process validates single-env logic and handler changes against a real dbt environment to guarantee integration fidelity prior to code merges.

When validating MCP server deployments, operators must rely strictly on the packaged workflow, support pack, troubleshooting notes, and provenance links, meaning verification is constrained to provided assets without external integrations.

Before handing off verified MCP server changes, you need to review upstream workflow context, provenance links, and the packaged support pack to ensure full documentation of the end-to-end validation results.