Solution skill
mcp-server-motherduck: TypeError main() got an unexpected keyword argument 'result_format'
Complete solution
Shows how to fix mcp-server-motherduck: TypeError main() got an unexpected keyword argument 'result_format'. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For "TypeError: main() got an unexpected keyword argument 'resultformat'": the maintainer confirmed it and shipped 0.3.3 the same day fixing the result\format argument mismatch. Fix: make sure youre on 0.3.3 or newer.
TypeError: main() got an unexpected keyword argument 'result_format'Steps
- This was a bug in the 0.3.2 release, not your config. The maintainer confirmed it and shipped 0.3.3 the same day fixing the
result_formatargument mismatch. A reporter confirmed "v 0.3.3 worked!". - Fix: make sure youre on 0.3.3 or newer. If you pinned the version in your Claude config, bump it:
{
"mcpServers": {
"motherduck": {
"command": "uvx",
"args": ["mcp-server-motherduck@0.3.3", "--db-path", "md:"]
}
}
}- Also double check
uvitself is installed, since the server runs throughuvx.
Expected: The maintainer confirmed it and shipped 0.3.3 the same day fixing the result\_format argument mismatch.
When to use
You are seeing this: Setting up the MotherDuck MCP server with Claude Desktop (access token plus home directory path per the README) wouldnt connect. Use this skill when you run into "mcp-server-motherduck: TypeError main() got an unexpected keyword argument 'result_format'".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: mcp-server-motherduck 0.3.0, 0.3.2, shipped 0.3.3. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/motherduckdb/mcp-server-motherduck/issues/6
Evidence
Someone asked: 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 'result_format'. Downgrading to mcp-server-motherduck==0.3.0 made it work, so the bug was in the 0.3.2 release. The verified resolution: This was a bug in the 0.3.2 release, not your config. The maintainer confirmed it and shipped 0.3.3 the same day fixing the result_format argument mismatch. A reporter confirmed "v 0.3.3 worked!".
Fix: make sure youre on 0.3.3 or newer. If you pinned the version in your Claude config, bump it:
{
"mcpServers": {
"motherduck": {
"command": "uvx",
"args": ["mcp-server-motherduck@0.3.3", "--db-path", "md:"]
}
}
}Also double check uv itself is installed, since the server runs through uvx. Thread: https://vectle.com/threads/thr_1vD8leyNUATGjWTmtPoEXg
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_g9mZExNsEuioTNL8-Lg8yw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">mcp-server-motherduck: TypeError main() got an unexpected keyword argument 'result_format' <span>— Vectle</span></a>