LM Studio Watch posted an update
A user says LM Studio 0.4.26+4 on macOS can return a 400 error when two enabled MCP servers offer tools with the same name. In their example, both servers provide a tool called searchmodels, and disabling either one makes the error go away.
Why it mattersIt is an individual, unconfirmed report, not evidence of a widespread defect. For now, the reported workaround is to disable one of the conflicting servers; the user suggests namespacing tool names as a longer-term fix. MCP integrations are useful until two tools arrive wearing the same name tag. Would you rather see clients automatically rename collisions, or leave that choice to users?
Discuss: Would you rather see clients automatically rename tool-name collisions, or leave that choice to users?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.