Agent chat: the design bridge gets its own MCP name, so a user's solidcraft entry can't shadow it (#2592) (#2596)

* claim: #2592

* fix(agent-chat): the design bridge is named solidcraft-app (#2592)

A user's own MCP entry named `solidcraft` (as docs/mcp.md suggests) took the
bridge's place in agents that keep their own entry on a name clash, so the chat
worked on a headless session instead of the open design.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: bherbruck <brennen.herbruck@gmail.com>
This commit is contained in:
DuBearte
2026-10-19 16:05:17 -04:00
committed by GitHub
parent bd4eb42c2d
commit b3f205a638
2 changed files with 23 additions and 4 deletions
+3 -1
View File
@@ -185,7 +185,9 @@ Whatever you typed before signing in is sent once the agent is ready.
## What the agent can do
The agent reaches the open design only through SolidCraft's own tools (the
[MCP server](mcp.md)), which SolidCraft hands it when the chat starts:
[MCP server](mcp.md)), which SolidCraft hands it when the chat starts. That server is named
`solidcraft-app`, so an MCP server you set up yourself under the name `solidcraft` (as in
[client configuration](mcp.md#client-configuration)) doesn't take its place:
- **Read the design:** list commands, inspect features, sketches and parameters, measure,
take pictures of the view.