Mistral (Le Chat)

Mistral Le Chat lets you add any remote MCP server as a custom connector: you paste the server URL, Le Chat auto-detects how it authenticates, and the connector’s tools become available in your chats. Connectors are available on all Le Chat plans, including Free. Adding one is an administrator action; on Free, Pro, and Student plans the account owner is the admin by default.

For developers, Mistral La Plateforme / Studio exposes the same custom-MCP mechanism through its Connectors API, so Engram’s tools can be called from the Conversations and Agents APIs. Both routes are covered below.

Protocol background lives at MCP.

Prerequisites

Before you start, confirm:

• You have an Engram account at app.engram.page.
• At least one vault is synced. Open the Obsidian plugin or the web app and confirm notes have synced within the last day.
• You can sign in via browser. The MCP auth flow opens a browser window.

Plus the Mistral-specific:

• A Le Chat account at chat.mistral.ai, any plan.
• Administrator rights in your Le Chat organization (the account owner on Free/Pro/Student).

Endpoint

https://mcp.engram.page

Setup (Le Chat)

1. Open Connectors. Go to the Connectors page, click + Add Connector, and switch to the Custom MCP Connector tab.

2. Fill in the form.

Connector name: engram          (no spaces or special characters)
Server URL:     https://mcp.engram.page
Description:    My Engram vault  (optional)

3. Connect. Click Connect. Le Chat probes the URL and auto-detects the authentication method. Engram advertises OAuth 2.1 with dynamic client registration, so Le Chat runs the OAuth consent flow: your browser opens to sign in to Engram and approve the connection. No app to pre-register, no token to copy. The grant is the full mcp scope today; granular per-action scopes are on the roadmap.

4. Set per-function permissions (optional). Open My Connectors → Engram → Functions and toggle Always allow for the tools you want pre-authorized. Engram exposes read functions (search, get a note, list folders) and write functions (create or edit a note). Pre-authorize reads you use often; keep writes on manual approval until you trust the flow.

Try it

In a chat, make sure the Engram connector is enabled, then ask:

• Search my vault for notes about the engineering interview process and summarize the top three.
• Find anything I wrote about embeddings in the last month.

Le Chat calls Engram’s search (or get_note, write_note, etc.) tool, pulls back results, and answers in-context.

La Plateforme / Studio (developers)

Mistral’s Connectors API lets you register a custom MCP server in Studio and then call its tools from the Conversations and Agents APIs. Mistral brokers the MCP transport for you, so you don’t manage it in your own code.

1. In the Studio console: Connectors → + Add Connector → Custom MCP Connector.
2. Set Server URL to https://mcp.engram.page and Connect.
3. Reference the connector in your API/SDK calls so the model can discover and invoke Engram’s tools.

For a server-to-server backend there’s no browser to run OAuth in, so authenticate with an Engram API key instead. Le Chat and Studio also accept an HTTP Bearer token when the URL is probed; generate a key at app.engram.page/settings/api-keys and treat it like any service credential: keep it out of source control and rotate it when teammates rotate off. See MCP Config → API Key Authentication.

Transports

Mistral’s custom MCP connectors use Streamable HTTP, the current MCP standard. Engram’s endpoint speaks Streamable HTTP, so pass the URL directly, with no adapter and no /sse path needed.

Current limitations

Mistral’s custom MCP connectors don’t yet support every MCP capability. At time of writing they omit dynamic tool discovery, resources, and automatic prompt templates. Engram’s core search/read/write tools work today; the omitted capabilities aren’t required for them. Mistral has said support is planned.

Troubleshooting (Mistral specific)

• “MCP connection requires additional information or is invalid.” Confirm the URL is exactly https://mcp.engram.page (no trailing path), reachable over HTTPS with a valid certificate, and that you completed the auth prompt. For OAuth, leave any credential field blank and let auto-detect run the browser flow.
• It asks for an API key instead of opening a browser. That’s the API-key (HTTP Bearer) path, fine for headless use. Paste an Engram key from settings. For the browser flow, remove the connector and re-add it without supplying a key.
• Tool calls never fire. The function may be on manual approval. Approve it in the chat, or set Always allow under the connector’s Functions tab. Or the model didn’t reach for the tool; prompt it explicitly to “use the Engram tools to look up my notes.”
• 401 from the connector. Your Engram API key (Bearer path) is wrong or revoked. Generate a fresh key in Engram settings.

For cross-client failures, see Troubleshooting.

Revocation

To disconnect Le Chat from Engram:

1. In Le Chat, find the connector or MCP server entry and remove it.
2. In Engram, open your account → API Keys & Sessions and revoke the matching session.
3. The OAuth token is invalidated server-side. Le Chat will need to re-authenticate to reconnect.

You can also remove the connector from the Connectors page in Le Chat itself.

Next steps

MCPProtocol overview.

ScopesWhat the grant covers.

All integrationsPick a different client.