feat: add --config-path flag to claude-desktop install command#3380
Conversation
--config-path flag to claude-desktop install command
jlowin
left a comment
There was a problem hiding this comment.
Thanks for the PR! The plumbing looks good.
One thing I'd like to see fixed before merging: when a user provides --config-path and the path doesn't exist, they currently get the generic "Claude Desktop config directory not found, please ensure Claude Desktop is installed..." message — which is confusing since they explicitly told us where to look. Could you add a distinct error for that case? Something like "The specified config path does not exist: {path}".
|
Implemented in d7aebb3
|
Test Failure AnalysisSummary: The Windows CI job failed due to a test timeout in Root Cause: The 6th test in Suggested Solution: This appears to be a pre-existing flaky test on Windows, unrelated to the
This PR's changes (CLI flag addition) are not the cause. Detailed AnalysisFailed job: Timeout log excerpt: Thread dump shows all workers blocked: Test configuration:
Related Files
|

Description
Currently,
fastmcp install claude-desktopfails for users who have Claude Desktop installed in a non-standard location, because the tool only checks hardcoded OS-specific paths.This PR adds an optional
--config-pathflag to thefastmcp install claude-desktopcommand, allowing users to manually specify their Claude Desktop config directory.Changes made:
--config-pathparameter toclaude_desktop_command()get_claude_config_path()to accept an optional Path overrideinstall_claude_desktop()to pass config_path throughContributors Checklist
custom configpath for 'fastmcp install claude-desktop' #3346Review Checklist
Screenshots
Testing
--config-pathflag locally (shows both default failure and successful install with custom path):