[vibe report] my experience just now

[dataders]

What happened?

I just had a surprise because my previously configured, globally-installed, dbt-mcp setup was clobbered by another configuration that was committed directly to the repo I was using (https://github.com/dbt-labs/internal-analytics/pull/4037)

the output of claude --debug had these lines in it. It was strange bc --env-file wasn't in my config at all, which led me to discover the project's .mcp.json

However, the error was coming from uv! Given the root cause of yesterday's struggle (#571) being that dbt-mcp was out-of-date, my first thought was maybe I have an old version of uv? Lo and behold my uv was 4 minor releases behind (0.5.3 -> 0.9.28)

Upgrading to latest resolved my issue completely. However, I can't help but feel that if dbt-mcp were to log the location of the config file being used it would be quite helpful.

Steps to Reproduce

see above

Deployment

Remote MCP server

Environment

No response

Relevant log output

2026-01-31T18:27:03.118Z [DEBUG] MCP server "dbt": Starting connection with timeout of 30000ms
2026-01-31T18:27:03.135Z [ERROR] MCP server "dbt" Server stderr: error: unexpected argument '--env-file' found

  tip: a similar argument exists: '--no-offline'

Usage: uvx [OPTIONS] [COMMAND]

For more information, try '--help'.
2026-01-31T18:27:03.135Z [DEBUG] MCP server "dbt": Connection failed after 18ms: MCP error -32000: Connection closed
2026-01-31T18:27:03.135Z [ERROR] MCP server "dbt" Connection failed: MCP error -32000: Connection closed

[b-per]

0.5.3 -- released on Nov 19, 2024

That's a lifetime away from a uv point of view 🤣

Upgrading to latest resolved my issue completely. However, I can't help but feel that if dbt-mcp were to log the location of the config file being used it would be quite helpful.

What config file are you referring to here?
The file where the MCP server is configured?

But we can also definitely recommend updating uv to the latest version in our docs.