How do I review C# MCP client package roles before adding Montage?
An outbound C# Montage connection should not require converting the application into an MCP server. Review the existing package roles and installed client API before adapting examples, preserving project dependencies and separating foundational client facilities from optional hosting components. Package references should explain which existing client facilities the application uses. Core, main and AspNetCore roles matter, but adding hosting components is not a remedy for an outbound transport or Montage account-authorization failure in a client application.
Help me review C# MCP client package roles before adding Montage. Read the project file and available lock information to identify official MCP packages and versions. State the package generation and real workspace response or blocker, with cleanup completed where possible. No writes.Inspect project references
Read the project file and available lock information to identify official MCP packages and versions. An AspNetCore reference elsewhere in the solution does not establish which client APIs this application already uses.
Separate package responsibilities
Distinguish Core foundations, main-package higher-level facilities and AspNetCore server hosting in the installed documentation. A route-registration sample is not the same operation as opening an outbound Streamable HTTP client to Montage.
Preserve the outbound boundary
Use the documented client transport for the hosted HTTPS endpoint without adding server hosting to copy a sample. Keep any supported approved application auth associated with that client rather than confusing local web-app identity with Montage permission.
Validate a direct read
Within the documented async lifetime, discover and execute signals_status without model inference. A successful build or initialized object is not enough to prove the selected packages can perform the authorized workspace operation.
Report the installed path
State the package generation and real workspace response or blocker, with cleanup completed where possible. This review does not authorize package additions or certify unrelated applications merely because they share the same solution file.
Keep the boundaries clear.
- Keep any supported approved application auth associated with that client rather than confusing local web-app identity with Montage permission.
- This review does not authorize package additions or certify unrelated applications merely because they share the same solution file.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.