Skip to content

fix/lmstudio-numeric-password-mcp - #172

Open
david-hummingbot wants to merge 3 commits into
mainfrom
fix/lmstudio-numeric-password-mcp
Open

fix/lmstudio-numeric-password-mcp#172
david-hummingbot wants to merge 3 commits into
mainfrom
fix/lmstudio-numeric-password-mcp

Conversation

@david-hummingbot

Copy link
Copy Markdown
Contributor

Summary

  • Coerce Hummingbot MCP username/password (and related CLI args) to strings when building stdio server configs, so YAML-loaded numeric credentials (e.g. password: 123456) don’t break agent startup.
  • Harden PydanticAIClient by stringifying MCP args/env before StdioServerParameters validation — the failure path used by lmstudio: / ollama: / other pydantic-ai backends.
  • Add a regression test covering numeric username/password credentials in MCP args.

Root cause

Unquoted numeric passwords in config.yml (often written by setup-environment.sh) load as int. Starting an LM Studio (pydantic-ai) session validates MCP args strictly and fails with:

StdioServerParameters.args.9 … input_value=123456, input_type=int

ACP agents don’t hit the same validation, so the bug mainly shows up with local LLMs.

Test plan

  • Set servers.local.password: 123456 (unquoted) in config.yml, restart Condor, start /agent with LM Studio — session should start (no StdioServerParameters error)
  • Confirm Claude/ACP agent start still works
  • Restore a real password afterward

Ensure all arguments and environment variables are strings.
Refactor to use _hummingbot_mcp_args for argument construction.
Add test for handling numeric credentials in MCP args.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant