Repository navigation
Conversation
Add an MCP tool that maps one model port to another model port, as a
manual mapping line does. ConfigurationDesk's ConnectObjects applies the
mapping rules; the server implements none.
- compatible: link created, no new conflicts
- warning: link created; warnings use the Conflicts Viewer wording and
effect from ExportConflictsToXML
- unknown: link created, but the conflict export after connecting failed
- MAPPING_REFUSED: ConfigurationDesk refused the mapping ("Cannot
connect"); its message is returned unchanged, no link is created. Other
ConnectObjects exceptions use the normal error handling.
Ports are addressed by model, model port block (name or hierarchy path)
and port path through port groups. Blocks ConfigurationDesk adds to the
signal chain are reported. Conflicts suppressed in the ConfigurationDesk
options (by default "Mismatching data type") are not reported.
list_model_ports keeps ports/count unchanged and adds paginated
leaf_ports with port_path, port_block_path and full_path for ports nested
in port groups.
Update tests, MCP inventory, tool map, tool docs, prompt guidance and
documented tool counts (79 tools).
Add an MCP tool that maps all name-matching ports of two model port blocks or port groups, like dragging one connector square onto another in the ConfigurationDesk UI. ConfigurationDesk's ConnectObjectsAutomatically pairs the ports; the server implements no matching rules. - Ports are paired by name, also in nested port groups; the order of the two sides does not matter. - Pairs are connected regardless of data type or width; mismatches are reported as warnings per link. - Inports that already have a source are skipped; existing links stay. A repeated call creates nothing new. - Status: compatible, warning, nothing_connected, or unknown (links created, conflicts could not be read). - Result lists created links with warnings, unconnected ports, links outside the two sides, and blocks added to the signal chain. - Blocks with the same name at the same level are told apart by an optional direction (inport/outport). Fix the port_type description of list_model_ports (raw PortType values). Update tests, MCP inventory, tool map, tool docs, prompt guidance and documented tool counts (80 tools).
Smaller models asked the user which model contains a named model port block, although list_models and list_model_port_blocks can find it.
imdshr
reviewed
Nov 12, 2026
imdshr
approved these changes
Nov 16, 2026
IZacharias
reviewed
Nov 19, 2026
IZacharias
reviewed
Nov 19, 2026
IZacharias
reviewed
Nov 19, 2026
IZacharias
reviewed
Nov 19, 2026
IZacharias
suggested changes
Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two MCP tools for model communication, so a user can ask the agent to
connect model ports of two models the same way as in the ConfigurationDesk UI:
(like drawing a mapping line manually).
block or port group to another one; ConfigurationDesk pairs the ports by
name (like dragging one connector square onto another).
Both tools report the result as in the UI: created links, warnings in the
Conflicts Viewer wording (e.g. "Mismatching data width"), and refused
mappings. ConfigurationDesk applies all mapping rules; the server implements
none.
list_model_ports additionally returns ports nested in port groups with
their paths, so the agent can address them. The agent now also looks up which
model contains a named block instead of asking the user.
Validation
uv run ruff check .uv run ruff format --check .uv run pytest ConfigurationDeskMCP/testsuv run configurationdesk-mcp --list-tools