Mistral

Mistral Work adds a custom MCP connector by server URL. Studio registers that URL as a connector for the API.

What the docs say

Work's custom MCP connector takes a server URL. The platform detects no auth, an Authorization header, or OAuth 2.1 with dynamic client registration. Featured connectors on the Work connectors page use a direct OAuth flow. Studio registers an MCP server URL for conversations and agents. The MCP directory is described as a third-party collection, and that page does not print its names.

Auth. Work auto-detects no authentication, HTTP Bearer or Basic, or OAuth 2.1 with dynamic client registration. Studio can send headers and OAuth client id and secret.

Limits from the docs

An administrator adds an MCP connector in Work. On Free, Pro, and Student plans the account owner is the administrator.
Studio connector visibility can be private, workspace, or organization.
The MCP Connectors directory is a curated third-party collection. Its names are not printed on the page checked here, so they are not copied.

Setup

In Work, open Connectors, Add Connector, and the Custom MCP Connector tab.
Enter a connector name and the server URL, then connect and finish the detected sign-in.
In Studio, create a connector with the server URL and a visibility scope.

Sources

Mistral Work connectors Checked 2026-10-17
Mistral Work MCP connectors Checked 2026-10-17
Mistral Studio connectors Checked 2026-10-17
Mistral beta connectors API Checked 2026-10-17

Compatibility rule

A listing is included when its directory transport token is one this platform's docs describe. The token is SSE when the transport label contains “sse”; otherwise HTTP when the label contains “http” or the listing has a hosted remote endpoint; otherwise stdio when the label contains “stdio”; otherwise undeclared. Undeclared listings are left out. This is a transport match, not a connection test. MCPwell has not run these servers inside this platform.

Directory transports counted here: remote HTTP. Only hosted remote listings are included.

The documented custom connector is a server URL, so only hosted remote HTTP listings are included. SSE is not named on the Work page we checked.

Officially listed is a separate mark. It is used only when this platform's own directory or connector gallery names that server and the name matches one listing in this directory. A sentence in a setup example is not a gallery listing. The mark is not a connection test.

MCP servers (23,049)

Paid placements appear first and are labelled Sponsored or Featured; the rest are sorted by GitHub stars. Sorted by GitHub stars as of 2026-10-17. Servers with no public GitHub repo follow, in alphabetical order.

Official or reference Hosted (remote) endpoint

The first 60 cards are in the page HTML. With JavaScript, the filters page all 23,049 compatible listings.

Mistral

What the docs say

Limits from the docs

Setup

Sources

Compatibility rule

MCP servers (23,049)

Paperclip

Nextchat

World Monitor

Netdata

Front-End Checklist

Context7 (Upstash)

Metabase

Reactive Resume

GitHub

Agent Skills Search Server

OpenWork MCP Gateway

Oh My Posh Validator

Skyvern

Compiler Explorer

Keploy

GitDiagram

Coder

MCP Toolbox

MCP Toolbox for Databases

OpenMetadata

Inbox Zero

Apify

Mobilerun

Nhost

openstatus

AIHOT

Sui Knowledge Base (kapa Ai)

Honcho

Firecrawl

Agent-Native Analytics

Business Contact Finder

Basebalance Cloud — X402 Rpc & Gateway

Openshorts

Airweave Search

Klavis

Treg To

Draw Io

Finance Toolkit

Ask Jev

Google Ads + Meta Ads + Ga4

Exa

Jitsu

Tradingview

Mockserver Monorepo

Tolgee

NotFair-GoogleAds

Radar

Grafana

RevoGrid DataGrid MCP Pro

ShipSwift

Butterbase Oss

Supabase

Omnara

Vexa

Wacli

Medplum

Korean Law MCP

Semiotic

Usertour MCP Server

BoostedTravel

First-party connectors