You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] MCP server fails with FastMCP 2.8.1 - unexpected keyword argument 'log_level' #164
Activity
potatopotaro commentedon Jun 21, 2025
Oops, my Claude code made this on its own, so sorry. Still debugging.
groksrc commentedon Jun 23, 2025
This is likely fixed in #150 and will be available in the next release.
adamdrzewiecki commentedon Jun 25, 2025
I don't think it's the same.
I built the server from the main repo, but when I try to run it with the stdio transport, it throws:
phernandez commentedon Jun 25, 2025
@claude can you look at the user the error is reporting an come up with a suggestion?
claude commentedon Jun 25, 2025
Claude finished @phernandez's task —— View job
Analyzing MCP Server Compatibility Issue
I've analyzed the FastMCP 2.8.1 compatibility issue and identified the root cause and solution.
Todo List:
Root Cause Analysis
The issue occurs in
src/basic_memory/cli/commands/mcp.pyat lines 79 and 89 wheremcp_server.run()is called withlog_level="INFO":The Problem:
log_levelparameter was added to fix deprecation warnings (as mentioned in commit 7be001c)log_levelparameter in itsrun_stdio_async()methodTypeError: FastMCP.run_stdio_async() got an unexpected keyword argument 'log_level'log_levelcauses the server to loop infinitely because the underlying issue isn't addressedCurrent Constraint:
fastmcp>=2.3.4inpyproject.toml(line 33)Proposed Solution
I recommend implementing a version-aware parameter handling approach. Here are the options:
Option 1: Version Detection (Recommended)
Option 2: Try/Except Approach (Simpler)
Option 3: Pin FastMCP Version (Conservative)
Update
pyproject.tomlto pin to a specific version range that supportslog_level:Recommendation
I recommend Option 1 (Version Detection) because:
Would you like me to implement this solution?
phernandez commentedon Jun 26, 2025
I'm fixing this right now.