Skip to content

Montage for Mistral Studio connectors

Mistral's current connector documentation describes Studio connectors for SDK and API conversations, not a promise about every Le Chat interface.

Integrations

How do I verify Montage workspace access with Mistral Studio connectors?

Mistral's current connector documentation describes Studio connectors for SDK and API conversations, not a promise about every Le Chat interface. A connector registers an MCP server so Mistral can discover and invoke tools without an application-managed MCP client. Because the feature is in Public Preview, keep version drift and connector visibility explicit, and verify Montage authorization separately from the API key that authorizes access to Mistral.

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
Mistral Studio connectors · read-only verification prompt
Using Mistral Studio connectors, call only Montage signals_status as the first live operation. Report the actual workspace identity and coverage from the tool response. If authentication, transport, or the tool is unavailable, stop and explain the blocker. Do not start collection, recurring tracking, writes, publishing, messaging, or social actions.
01 / Integrations

Use the Studio connector workflow

Start from Mistral Studio's current Connectors documentation and inspect the Quickstart and Manage connectors links for your API version. Do not translate the former Le Chat candidate URL into unsupported consumer settings. This path registers a hosted server for Studio conversations and agents. Decide who owns the connector and whether it should be private before making it available to an application or workspace.

02 / Integrations

Register the hosted MCP address

Supply https://app.montages.co/mcp through the documented connector registration workflow, choosing visibility deliberately. Registration is not the same as creating a local client process, so a stdio command does not belong here. The overview says a connector can discover server tools, but that capability is not a certification of Montage compatibility or proof that your account has permission to execute workspace-scoped requests.

03 / Integrations

Distinguish the two authorization layers

Mistral API keys have connector access scopes; the default Shared connectors only scope does not include private connectors. Confirm the application's existing key is permitted to use the chosen connector without widening its scope as a troubleshooting shortcut. Separately establish the remote authentication Montage requires using documented connector authentication support. If that path is incompatible, stop; possession of a Mistral key does not sign in to Montage.

04 / Integrations

Prefer a controlled direct tool test

The connector overview links a direct tool-calling path as well as model-driven conversations and human-in-the-loop controls. Use the documented direct route for initial status verification when available, selecting the actual signals_status schema. If testing through a model instead, keep available tools narrow and approvals explicit. A connector's discovered catalog should never be interpreted as standing approval for every newly published server tool.

05 / Integrations

Inspect status before conversation rollout

Make the first live Montage operation signals_status and compare its returned workspace with the connector owner's intent. Distinguish a Mistral connector-access denial from a Montage authorization denial in diagnostics. Do not distribute the connector or enable autonomous agents until that boundary is understood. Public Preview support is not live certification, and no automatic collection, recurring research, publishing, or social actions are part of this connection check.

Keep the boundaries clear.

  • The documented path is Mistral Studio connectors in Public Preview, not an assumed Le Chat UI; private connector scope differs from the default.
  • Documented setup, not live interoperability certification. A visible tool catalog is not workspace authorization.
  • First live operation: read-only signals_status. No automatic collection, recurring tracking, or social actions; broader actions need separate explicit authorization.

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.

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

Get started
montage