recce-mcp-e2e

Execute end-to-end verification of MCP server changes against a real dbt project.

108|27|Updated Mar 26, 2026

Search Tags:#workflow #testing #mcp #provenance #server #e2e-verification

Ready to run

npx skills add https://github.com/diegosouzapw/omni-skills --skill recce-mcp-e2e-diegosouzapw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: recce-mcp-e2e
Source: https://github.com/diegosouzapw/omni-skills/tree/main/skills/recce-mcp-e2e
Command: npx skills add https://github.com/diegosouzapw/omni-skills --skill recce-mcp-e2e-diegosouzapw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

MCP E2E Verification addresses the need to validate MCP server changes against a real dbt project, ensuring end-to-end reliability before deploying or merging changes.

Core Features & Use Cases

Provides full-stack verification for MCP workflows when server code, tool handlers, or single-env logic changes
Includes upstream workflow context, provenance, and a packaged support pack for review and handoff
Use Case: when MCP PRs are prepared or when operator needs to verify changes against a real dbt project

Quick Start

Invoke the MCP E2E workflow against your target dbt project to perform end-to-end verification.

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 changes against a real dbt project?▼

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.

What is end-to-end MCP verification and when do I need it?▼

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.

How do I run end-to-end tests for dbt project workflows before merging PRs?▼

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.

Can I use MCP verification workflows to test modified tool handlers?▼

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.

What limitations should I consider when validating MCP server deployments?▼

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.

What do I need to review before handing off verified MCP server changes?▼

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.