DYN-10868: Bump DynamoMCP to 0.6.1 - #17347
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
See the ticket for this pull request: https://autodesk.atlassian.net/browse/DYN-10868
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
No unresolved issues were identified.
Review effort: Lite
Findings: None
What changed in this PR
Updates DynamoCoreWpf to consume DynamoMCP 0.6.1.
Changes:
- Bumps the exact package version from 0.6.0 to 0.6.1.
- Preserves existing package-copy and isolation behavior.
| File | Description |
|---|---|
src/DynamoCoreWpf/DynamoCoreWpf.csproj |
Updates the hard-pinned DynamoMCP package reference. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
jasonstratton
approved these changes
Sep 24, 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.



Purpose
Lockstep bump of the hard-pinned
DynamoVisualProgramming.DynamoMCPbuilt-in package reference from[0.6.0]to[0.6.1], to consume the DynamoMCP 0.6.1 release. Same one-line shape as #17334 (0.5.9 → 0.6.0) and #17319 (0.5.8 → 0.5.9).Tracking task: DYN-10868.
0.6.1 is the largest DynamoMCP release to date — nine PRs, eight of them new MCP tools. The two items that matter most for Dynamo:
Added— bearer tokens are now verified against the issuing authority's published JWKS when the ADP Desktop SDK provides no MCP token validation, so Autodesk Assistant can drive Dynamo in Civil 3D. ADP Desktop SDK 7.0.x replaced the identity wrapper'sIDSDKWrapperwith a component whose onlyProcessMessagemessage isGetUserID;ValidateMCPTokenis gone, the wrapper answers a bare{"_returnCode": 2}, nothing evaluates the token and the gate fails closed. This is not Civil 3D-specific —AdpDesktopSDK\binis a junction to the newest installed SDK, so installing 7.0.x repoints it for every Autodesk product on the machine. The new tier verifies the RS256 signature,exp,nbfandaudwith no ADP or IDSDK dependency. It is a fallback, not a replacement: IDSDK is asked first and any verdict it renders is final, never retried against JWKS, so hosts where IDSDK works are unaffected and a genuine rejection cannot be worked around. Trust is pinned to the three known MCP auth hosts, redirects are disabled on the key fetch, andalgis pinned toRS256. One documented reduction in strength: thedevice-sessioncheck the native API performs is not reproduced, because its expected value lives inside Identity Manager and is not derivable from the token.Fixed— two undo-group teardown paths closed Dynamo's undo action group from a thread that was not Dynamo's.The eight new tools:
cancel_run,add_nodes_to_group,find_nodes,collapse_group,set_run_mode,get_node_value,export_screenshot,export_node_help_doc.One behaviour change worth a reviewer's eye, though it is confined to the MCP tool surface and not to Dynamo APIs:
set_node_valuenow fails with an explicit message on Date Time nodes and on parameterless zero-input nodes (e.g.Point.Origin) instead of reporting a success that never did anything. Dynamo exposes no working update key for them — neitherDateTimenor itsBasicInteractivebase overridesUpdateValueCore— so those calls only appeared to succeed.Verification performed against the published package:
dotnet restore src/DynamoCoreWpf/DynamoCoreWpf.csprojsucceeds andsrc/DynamoCoreWpf/obj/project.assets.jsonresolvesDynamoVisualProgramming.DynamoMCP/0.6.1under the exact-version pin, with no version-resolution errors.extra/MCP_ExtensionDefinition.xml.MCPServer.dllandMCPExtension.dlladvance, 0.6.0.0 → 0.6.1.0 (verified by comparingVersionInfo.FileVersionacross every DLL in both packages).MCPServer.dllgrows 459,608 → 803,672 bytes, which is the eight new tools plus the JWKS validator;MCPExtension.dllis byte-identical in size.Get-AuthenticodeSignaturereports Valid for bothMCPServer.dllandMCPExtension.dll..github/scripts/check_file_version.ps1lists the DynamoMCP assemblies by filename with no pinned versions, and 0.6.1 adds no new assembly, so its exclusion list is unaffected.Declarations
Check these if you believe they are true
bin-wrapped package layout and the lockstep-bump rule all remain accurate; no code added.Release Notes
Autodesk Assistant can now drive Dynamo in Civil 3D and on any machine running ADP Desktop SDK 7.0.x, where bearer-token validation previously failed closed. Adds eight assistant-facing capabilities: cancelling a run, finding nodes, reading a node's value, adding nodes to a group, collapsing a group, setting the run mode, exporting a screenshot, and exporting a node help doc.
Reviewers
@jasonstratton (reviewed #17307, #17314, #17319, #17334)
Notes: the only functional change in this diff is the pinned version string on line 2222; everything else above is verification evidence.
FYIs
Disclosure on the source release build: DynamoMCP's 0.6.1 pipeline went red at the
system_teststage, after the signing and NuGet-publish stages had already completed — the failure is a known intermittent race in the newexport_node_help_docintegration test, tracked as DYN-10957. The same code passed the same stage on its own PR build 38 minutes earlier. The published artifact is unaffected and independently verified above (contents, assembly versions, signatures), but flagging it rather than leaving it to be discovered.🤖 Generated with Claude Code