Connect Le Chat

    Mistral's chat product — launched as Le Chat, and documented as Vibe (with the workspace side called Vibe Work) since Mistral's 2026 renaming — connects to the gateway as a Custom MCP Connector. Mistral doesn't run a submission process for third-party servers to join its built-in connector directory, so configuring a custom connector in your own workspace — a two-minute form, no code — is the way in today. The steps below use the current Vibe UI names.

    Step 1 — add a custom MCP connector

    Open the Connectors page, click + Add Connector, and switch to the Custom MCP Connector tab. Fill in:

    Connector name:  Ansvar
    Server URL:      https://gateway.ansvar.eu/mcp
    Description:     EU law, regulation, and standards — cited answers

    Description is optional; the name and server URL are what Le Chat needs. Click Connect.

    Step 2 — authenticate

    Le Chat auto-detects a connector's authentication method — no auth, an HTTP bearer token or basic auth, or OAuth 2.1 with Dynamic Client Registration. The gateway advertises OAuth 2.1 with DCR, so clicking Connect should open a browser consent screen at auth.ansvar.eu on its own — approve it, and there's no client ID or secret to obtain by hand.

    Step 3 — use it in a conversation

    In a chat, click the + icon or type / in the input, select Tools, and enable the Ansvar connector — Mistral's current docs give exactly that flow. After that the gateway's tools are called when your question needs them — you don't select a tool by name, just describe what you need.

    Try a question

    Ask something with a citable answer, for example: "Using Ansvar, what does NIS2 require of an essential entity's incident-reporting timeline?" A grounded answer names the article and cites the fetched text, not Le Chat's own model memory.

    Which plans can add a custom connector

    Mistral's launch announcement for connectors describes them as "everything available on the Free plan" — no MCP-specific paywall is stated there or in Mistral's technical documentation. Mistral's docs do describe custom connectors as an administrator-only feature: on solo Free, Pro, and Student accounts the account owner is the administrator by default, so there's nothing extra to unlock; Team and Enterprise workspaces need an admin to add or approve one.

    Instruct your agent — the routing pack

    A connected agent without routing instructions can still answer legal questions from its training data — the connector sitting idle at exactly the moment it should prove itself — when a message does not name Ansvar. Paste the block below under Context → Instructions so new tasks carry it. The block is the same set that Instruct your agent explains line by line; adapt the jurisdictions to your market.

    You are a compliance research assistant. Answer legal, regulatory,
    and security-standards questions only from Ansvar tool results,
    never from your own knowledge.
    
    For every legal, regulatory, or standards question:
    1. Call the search tool, always with a scope: jurisdictions=["SE"]
       (adapt to your market; add "EU" for EU regulation - GDPR, NIS2,
       the AI Act), or frameworks=["GDPR"] for one EU framework across
       the board. On the Free plan, pass exactly one jurisdiction or
       framework per call.
    2. Never pass the user's whole question as the query. Reduce it to
       1-3 legal key terms in the language of the law you are searching
       - Swedish terms for Swedish law. Try alternative terms as separate
       searches. If a multi-concept query returns nothing, split it into
       one search per concept.
    3. If a search returns nothing, retry once with a synonym or a
       broader term, then retry with allow_broadening=true and label
       any relaxed matches as such.
    4. Cite every answer: law, article, and source URL from the
       results. If the results do not contain the answer, say which
       searches you ran and that you will not answer from memory -
       never invent a source.

    If something breaks

    • The tool catalogue looks incomplete, or doesn't reflect a tier change. Mistral's docs note that Custom MCP Connectors don't yet support dynamic tool discovery — remove and re-add the connector to pick up a changed tool list.
    • No Custom MCP Connector tab. This is an administrator-managed feature in Team and Enterprise workspaces — ask your workspace admin to add it or grant you access.
    • Tools are missing. Tools outside your Ansvar tier are absent by design — see the tool reference.
    • Everything else — the general troubleshooting page covers OAuth popups, quota errors, and empty results.