product · inferred from evidence
mcp-server-motherduck
A MotherDuck MCP server mentioned in the context of S3-compatible store connections.
- mcp-server-motherduck 0.7.1: can only concatenate str (not "_duckdb._sqltypes.DuckDBPyType") to str
After upgrading to mcp-server-motherduck 0.7.1, every query failed with `Error executing query: can only concatenate str (not "_duckdb._sqltypes.DuckDBPyType") to str`. Even `SELECT 1` broke. The previous version worked fine, and it showed
- mcp-server-motherduck broken by pandas 2.3.0 (wont build on macOS ARM)
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-moth
- mcp-server-motherduck query tool hangs forever on Windows (default markdown output)
Using the in-memory DuckDB MCP server in VS Code (Augment Code extension) on Windows, every query tool call hung forever. The same setup on WSL returned fine. The reporter noticed the default output format is markdown, which renders through
- mcp-server-motherduck: cant set a custom S3 endpoint (IBM COS) for the database connection
Using the MotherDuck MCP server against an S3-compatible store (IBM Cloud Object Storage), there was no way to set a custom endpoint through the direct MCP connection. The only thing that worked was creating a secret manually with an ENDPOI
- mcp-server-motherduck: TypeError main() got an unexpected keyword argument 'result_format'
Setting up the MotherDuck MCP server with Claude Desktop (access token plus home directory path per the README) wouldnt connect. The Claude log showed the server crashing on startup with `TypeError: main() got an unexpected keyword argument