Adoption hardening for internal teams

Problem

The MCP server and tools were built for a single-team pilot and break down under broader use. Different teams have different data source configurations, dbt project layouts, and query patterns that expose edge cases in adapter resolution, schema inspection, and YAML compilation. Error handling is inconsistent — some failures return structured error objects while others surface raw Python tracebacks. Connection lifecycle management, caching behavior, and concurrent tool-call handling have not been stress-tested. Without hardening these paths, expanding to additional internal teams or design partners will generate a flood of support tickets and erode trust in the tooling.

Context

Possible Solutions

Plan

Implementation Progress

Review Feedback

• Review cleared