Support

Le Chat (Vibe) Setup

Connect Tempreon to Mistral's assistant — renamed Vibe, with connectors now under Work — so it can load your Core Imprint, search your Knowledge Vault, and remember what it learns.

Ready to connect? Your Bridges page walks you through it step by step.

Open your Bridges page

Overview

Vibe is Mistral's AI assistant, and it is what Le Chat is now called. It supports custom MCP connectors with automatic authentication detection — including OAuth 2.1 with dynamic client registration, which is exactly what Tempreon speaks — so setup is a short form with nothing to configure by hand.

Naming note: Le Chat is now Vibe. chat.mistral.ai is still the entry point and existing plans carried over, but the product has three modes — Work, Code, and Chat — and Connectors live under Work. Mistral's documentation moved with the rename: the old /le-chat/* paths now redirect to /vibe/*. This guide uses the current labels.

Once connected, your AI loads your Core Imprint, searches your Knowledge Vault, and remembers what it learns — across every tool. Insights you store from Vibe surface in Claude, ChatGPT, or any other connected client, and vice versa.

Quick path: Work → Connectors → + Add Connector → Custom MCP Connector tab → name + server URL → Connect → authorize.

Prerequisites

  • A Mistral account. Custom MCP connectors are available on Free, Pro, Team, and Enterprise plans — there is no plan gate on this feature, though Mistral currently labels it beta
  • Administrator access. Adding a connector is an admin action; on Free, Pro, and Student plans the account owner is the administrator by default, so you can add it yourself. On Team and Enterprise, an admin adds it
  • A Tempreon account with at least one available Bridge slot
  • Your Tempreon MCP server URL (also shown in your Bridges dashboard)

Step-by-Step Setup

1. Open the Connectors page

In Vibe, go to Work, open the Connectors page, and click + Add Connector.

2. Add a custom MCP connector

  1. Switch to the Custom MCP Connector tab
  2. Connector name: Tempreon — no spaces or special characters
  3. Server URL:
https://api.tempreon.com/functions/v1/tempreon-mcp/mcp
  1. Description (optional) — a short note on what the connector does
  2. Authentication is detected automatically — Vibe recognizes Tempreon's OAuth 2.1 with dynamic client registration, so there are no keys or credentials to enter
  3. Click Connect

3. Authorize the connection

Complete the browser consent flow when prompted: sign in to Tempreon, review the request, and approve.

4. Decide what gets pre-authorized

Every Tempreon function is available as soon as the connector is live. What you control here is whether Vibe asks first: open My Connectors, click the Tempreon card, open the Functions tab, and toggle Always allow for the functions you'd rather not approve one at a time.

Mistral's own guidance is to pre-authorize reads and keep writes on manual approval to begin with. For Tempreon that maps cleanly: Always allow on session_start and search, which run constantly and only read; leave remember and log_work prompting until you trust the pattern.

Worth knowing: adding the connector is admin-only, but this toggle is per-user — each person sets their own.

A current limitation: the tool list doesn't refresh itself

Mistral lists dynamic tool discovery as not yet supported for custom MCP connectors, alongside Resources and automatic prompt templates. The practical effect is that the tool list Vibe holds for Tempreon won't update on its own — tools added by a later Tempreon release won't appear until the connector is registered again.

Removing and re-adding the connector picks up the current list. (Editing and re-saving in place is our own field observation rather than something Mistral documents, so try it first if you prefer, but the reliable route is a clean re-add.)

Troubleshooting

"MCP connection requires additional information or is invalid." Mistral names four causes for this error: the endpoint path (some servers use /mcp, others /sse — Tempreon uses /mcp), server reachability over HTTPS with a valid TLS certificate, authentication (an OAuth server should return a 401 with a WWW-Authenticate header), and the MCP handshake — the server must respond correctly to the initialize JSON-RPC call.

The connector won't accept the name. Connector names take no spaces and no special characters. Tempreon works.

Tools seem to be missing. Custom connectors don't do dynamic tool discovery yet — re-add the connector to pick up the current list (see above).

Vibe asks before every Tempreon call. That's the default. Toggle Always allow on the functions you use most, under My Connectors → Tempreon → Functions.

Also connect: Perplexity · Grok · ChatGPT

Try saying...

  • "Start my session." — triggers session_start to load your Core Imprint
  • "What do you know about me from Tempreon?" — a quick end-to-end test
  • "Remember that [decision] — we chose it because [reason]." — stores the insight for every connected client

Frequently asked questions

How does authorizing Tempreon work in Vibe?
Vibe detects the authentication method automatically — it recognizes Tempreon's OAuth 2.1 with dynamic client registration, so there are no keys or credentials to enter. After you click Connect, complete the browser consent flow: sign in to Tempreon, review the request, and approve. Every Tempreon tool is then available; the per-function Always allow toggle only decides whether Vibe asks you for approval each time it calls one.
Where do I add the Tempreon connector in Vibe, formerly Le Chat?
Connectors live under Work. Open the Connectors page, click Add Connector, then switch to the Custom MCP Connector tab. Enter Tempreon as the connector name, which can't contain spaces or special characters, paste the server URL, optionally add a description, and click Connect. Adding a connector is an administrator action, and on Free, Pro, and Student plans the account owner is the administrator by default, so you can do it yourself. On Team and Enterprise plans an admin adds it.
Some Tempreon tools are missing in Vibe after an update. How do I fix it?
Mistral lists dynamic tool discovery as not yet supported for custom MCP connectors, so tools added by a later Tempreon update won't appear on their own. Removing and re-adding the connector picks up the current tool list. Note that a tool being present but not pre-authorized is a different thing — it still runs, Vibe just asks you to approve the call first.