Skip to content

Montage for the MCP C# SDK

Select the official C# SDK's client components, configure application-owned HTTP authorization, and validate Montage without assuming enterprise SSO.

Integrations

Which C# components and authorization boundary does a Montage client need?

The official C# SDK supports MCP clients, but its Core, main and AspNetCore packages serve different roles. Connecting to Montage is a client task; adding server hosting components does not establish remote authorization. Your application must supply an approved HTTP auth path. In particular, an enterprise identity assertion is not an automatic Montage sign-in method, even when both systems are used by the same organization.

01 / CONFIGUREOne remote endpointUse this client's documented HTTP setup
02 / AUTHORIZEYour workspace accessUse a supported sign-in or credential flow
03 / VERIFYRun signals_statusCheck a real workspace response
C# MCP client · remote Streamable HTTP endpoint
https://app.montages.co/mcp
Final read-only client check
Using approved application HTTP authorization, execute signals_status and inspect its actual workspace response. Stop on auth or transport failure; do not assume enterprise identity grants Montage access.
01 / Integrations

Inspect existing package references

Read the application's project file and dependency lock information to determine which official MCP packages and versions it already uses. Distinguish Core's foundational APIs, the main package's higher-level facilities and AspNetCore server hosting. Follow the installed client documentation without adding packages or converting a client application into a hosted server merely to copy a sample.

02 / Integrations

Choose the documented HTTP client transport

Configure the installed SDK's remote Streamable HTTP client path with https://app.montages.co/mcp. Match transport and client APIs to the same package generation. A server-hosting sample, stdio process configuration or web application route registration does not describe this outbound connection. Keep the remote target explicit so that transport errors can be diagnosed separately from identity failures.

03 / Integrations

Supply approved Montage authorization

The application owns HTTP authentication and any supported OAuth lifecycle, including private credential storage and user association. Do not forward enterprise identity assertions as though Montage automatically accepts them, and do not confuse a model-service credential with workspace permission. If the required auth cannot be configured through supported facilities, return a clear unavailable state rather than weakening validation or sharing credentials across users.

04 / Integrations

Manage connection lifetime and discovery

Use the documented asynchronous client lifecycle and resource disposal for the installed SDK. Inspect the remote tool definitions while the connection is active and select signals_status for initial verification. Expose failures accurately to the calling application. An initialized client object or a list of tools is useful diagnostic evidence, but neither proves a successful authorized workspace operation.

05 / Integrations

End with authorized signals_status

Execute Montage signals_status through the configured client and inspect the real workspace and coverage response. If authorization is rejected, repair the application-owned auth path instead of adding server packages or assuming enterprise SSO. If transport fails, verify Streamable HTTP configuration, endpoint and disposal timing. Do not run collection, writes or model inference as a substitute, and leave the integration blocked until the read-only check succeeds.

Keep the boundaries clear.

  • Core, main and AspNetCore packages have distinct roles; server hosting is not required for this client connection.
  • Enterprise identity assertions do not automatically sign a user into Montage.
  • Application-owned HTTP authorization is required; documented setup is not live-certified interoperability.

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-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage