Getting your MCP server into Mistral’s Le Chat is the easiest connection on this list, and the one people most often get wrong. Any Le Chat administrator can drop your server’s URL into the connector settings and start using it in a couple of minutes. No form. No review queue. No waiting on anyone. So the real question isn’t whether you can get listed on Le Chat. It’s what you mean by listed, because there are three connector types and only one of them you can set up yourself.
Summary
- Adding the connector is self-serve - Any Le Chat administrator adds your remote MCP server by pasting its URL. Le Chat auto-detects the auth, from none to bearer token, basic auth, or OAuth with dynamic client registration. No application, no review.
- The curated directory is a separate door - Featured connectors and the MCP Connectors directory are Mistral-curated. The directory launched with 20+ connectors in September 2025, and there’s no public submission form for it. Getting in is a business-development conversation, not a button.
- Your server still has to clear the universal bar - Self-serve doesn’t mean low-bar. You still want a remote HTTPS endpoint on Streamable HTTP, OAuth with user consent, annotated tools, and a live privacy policy, because that’s what every stricter surface demands too.
- Start with the admin setup - Stand up the custom connector, write a short setup doc your customers can follow, and let usage build the case before you contact Mistral. See Tallyfy in action
Before you connect anything, be clear on what connecting actually buys you. A connector gives Le Chat a set of tools it can call. It doesn’t hand over the order to call them in, or the rule for when not to call them at all. That sequencing is the process, and it’s worth pinning down first, which is the thread running through the AI and the future of work hub.
Le Chat has three connector types, one self-serve
Le Chat splits outside tools into three connector types, and they aren’t the same kind of thing. Featured connectors are the ones Mistral builds and maintains itself. The MCP Connectors directory is a curated set of third-party servers Mistral reviews, so a user can add them in a few clicks. And custom MCP connectors are the open door: an administrator points Le Chat at any remote MCP server URL and it works.
Mistral’s connector docs are blunt about what that last category is and isn’t. They also draw a hard line on who owns the risk: “MCP Connectors aren’t Mistral products. We don’t control third-party servers and can’t guarantee their behavior or data handling. Connect only to servers you trust.” Read that as your cue to make your server trustworthy on its own merits.
Conversational Workflow Made Easy
The split matters because it changes what you’re chasing. The custom tier you can use this afternoon. The directory and featured tiers you have to be invited into.
What you can switch on today, without asking Mistral
The custom connector path is the one you control end to end. An administrator opens the connector settings, pastes your server’s remote URL, and Le Chat takes it from there. It auto-detects how your server authenticates, whether that’s no auth at all, an HTTP bearer token, basic auth, or OAuth with dynamic client registration. On the Free, Pro, and Student plans the account owner is the admin by default, so for a small team it’s often one person and two minutes of clicking.
That’s the whole minimum. Paste a URL, approve the consent screen, done.
This is why the build matters more than the listing. Tallyfy’s server is a remote HTTPS endpoint with OAuth consent and dynamic client registration, so it drops into Le Chat as a custom connector with nothing to change on either side. The work that makes a custom connector painless is the same work every stricter program asks for, which means you do it once and reuse it everywhere. If you want the protocol background before any of that, our explainer on what MCP servers are covers the shape.
The build behind the two-minute connection
Self-serve isn’t the same as low-bar. The two-minute connection only feels easy because the demanding work already sits on your side of the wire. Get that package right once and it travels: the server that satisfies Le Chat is the same one that clears Anthropic and the rest.
What goes in the package? A cloud-hosted server reachable over public HTTPS. Streamable HTTP for transport, since the older SSE option is on its way out and gets turned away on stricter surfaces. OAuth that asks the user to consent rather than handing over blanket access. Tools that each carry a plain title plus the right annotation, a read-only flag for safe ones and a destructive flag for the ones that change data. A privacy policy that’s published and current. A working test login with real sample data behind it.
One more thing works in your favor across every program. Reviewers are wary of connectors that just pipe requests through to somebody else’s API, so a connector wired to your own product reads as first-party and sidesteps that suspicion. Say so plainly in your listing copy. For the mechanics of how an agent reaches those tools once connected, how agents talk to your tools over MCP walks it through.
Do you actually need the Featured directory?
Probably not first, and maybe not at all. The Featured connectors and the curated directory are Mistral’s call, not yours. There’s no public form to submit and no review you can enter on demand. Getting in is a partnership conversation: you reach out to Mistral, lead with the fact that your connector is first-party to your own product, and point at real user demand. The directory launched with more than 20 connectors in September 2025 and stays curated, so it’s a credibility upgrade rather than an access requirement.
Here’s the order that makes sense. Ship the custom connector now, because that’s the part that actually lets your users connect. Write the setup doc. Then, once you can show Mistral that people are already using your server inside Le Chat, the directory conversation has something behind it.
Demand first, directory second.
If Le Chat matters to your users, you don’t have to wait for anyone’s approval to serve them. Stand up the custom connector, hand your customers a short setup doc, and let real usage do the convincing before you ever email Mistral about the directory. The good part is that none of this work is Le-Chat-specific. What connects here is what you’d take into Claude’s Connectors Directory or submit as a ChatGPT app, both of which run a stricter review than Mistral’s open door. And if you want to see why the process behind the tools matters more than the connection itself, Tallyfy AI covers how an agent stays inside its guardrails once it can act.
Common questions about MCP connectors in Le Chat
Is adding an MCP server to Le Chat free and self-serve?
What authentication does Le Chat support for a custom connector?
How do I get into the Mistral MCP Connectors directory?
Are directory connectors maintained by Mistral?
Mistral is the surface where listing your server is least about Mistral and most about you. The door is already open, so the only thing standing between your users and your tools is whether your server is built to be trusted. Get that right, document the setup, and the directory becomes a conversation you have from a position of strength rather than a gate you’re stuck behind.
