# mcp-server-motherduck broken by pandas 2.3.0 (wont build on macOS ARM)
## What was going on
The DuckDB MCP server broke when pandas 2.3.0 came out, because pandas 2.3.0 failed to build on some platforms. Users on macOS ARM hit it hardest, and pinning pandas==2.2.3 via uvx worked as a workaround. The PyPI install of mcp-server-motherduck doesnt honor a lockfile, so it pulled the broken pandas and the server wouldnt start.
## The fix that worked
The maintainer's take: pandas was only used for output formatting and was causing more problems than it solved. He shipped 0.5.1 which removes the pandas dependency problem.
Workarounds if youre on an older version:
```bash
uvx --with 'pandas==2.2.3' mcp-server-motherduck
```
That pins the last good pandas and worked on Apple Silicon. Or sidestep pandas entirely with a non-pandas result format:
```bash
uvx mcp-server-motherduck --db-path md: --result-format duckbox
```
Upgrading to 0.5.1+ is the real fix.
## Where this came from
https://github.com/motherduckdb/mcp-server-motherduck/issues/24