Tech for RetailMeet us there
MyriadeMyriade

Connect Le Chat to your SQL Server database

Le Chat queries your SQL Server data through Myriade's MCP server: with business context, read-only, under each user's access rights.

Standard MCP · not tested by Myriade

Prerequisites

  • A Myriade account on app.myriade.ai (or on your self-hosted instance).
  • Network access from Myriade to SQL Server, with a read-only account.
  • Le Chat, on a plan that allows custom MCP servers (see the note in step 2).

1. Connect SQL Server to Myriade

Host, port (1433 by default), user and password. The database is optional: without one, Myriade discovers the other databases of the instance. A client-side query timeout can be set per connection.

Best practice: use a dedicated login, member of db_datareader on the relevant databases.

2. Add Myriade to Le Chat

Le Chat, Mistral's assistant (now called Vibe), supports custom MCP connectors added by URL, with OAuth or a bearer token.

  1. 1Take the Myriade MCP address: https://app.myriade.ai/mcp.
  2. 2Open Connectors → Add Connector → Custom MCP Connector, then enter a name without spaces and this URL.
  3. 3Click Connect: authentication is detected automatically, then sign in to Myriade.
https://app.myriade.ai/mcp

Only admins add custom connectors (on Free, Pro and Student plans, the account owner is the admin). Each tool call asks for approval by default.

Self-hosted Myriade (optional): replace app.myriade.ai with your instance's host.

3. Check the connection

Ask Le Chat a few questions:

  • “Which tables describe customer orders in SQL Server?” The assistant searches the Myriade catalog before writing SQL.
  • “What was revenue by region last quarter?” Read-only SQL, run under your access rights, saved in Myriade.
  • “Did any alert fire on our KPIs this week?” The assistant reads Myriade's checks and alerts.

What Myriade enforces

  • INSERT, UPDATE, DELETE, DROP… blocked; a query that cannot be parsed is rejected
  • Maximum duration per query and a cap on concurrent queries
  • At most 50 rows returned to the assistant
  • Database visibility, team rules on tables and columns
  • Protected columns stay masked, including for the assistant
Why connect through Myriade

Frequently asked questions

Can Le Chat modify or delete data in SQL Server?

No. SQL queries that Le Chat sends through Myriade's MCP server are parsed before they reach SQL Server: any write (INSERT, UPDATE, DELETE, DROP…) is rejected, even nested in a subquery, and a query that cannot be parsed is refused. As a precaution, also connect Myriade to SQL Server with a read-only account.

Does Le Chat connect directly to SQL Server?

No. Le Chat only talks to Myriade's MCP server: Myriade alone holds the SQL Server credentials and runs the queries. On Myriade Cloud, the MCP address is public and Myriade must be able to reach SQL Server. If you choose to self-host Myriade, the connection to SQL Server starts from your own infrastructure, and the MCP address must stay reachable by Le Chat.

Is Le Chat compatible with Myriade?

Le Chat supports remote MCP servers, and Myriade exposes a standard MCP server (Streamable HTTP, OAuth). Myriade has not tested this connection yet: tell us if you try it, we will help you set it up.

No Myriade account yet?

Book a demo to see Myriade on your own data.