5 min read

How to add a custom MCP connector to Le Chat

By Founder & Research Lead, Kalaris Labs · Updated

Le Chat can use tools from remote MCP servers you add as connectors. It detects whether a server needs authentication, so a public one connects in a few clicks.

This guide adds one, turns it on in a chat, and plans a product launch video from a real reference.

What a custom connector lets Le Chat do

  • Add a server by URL; Le Chat detects the authentication.
  • Turn connectors on per chat.
  • On Free, Pro and Student plans you are your own admin.
  • Read-only tools, nothing to sign in to.

Add a custom MCP server to Le Chat

The example here is a free library of real product-launch videos at https://kuchi.kalarislabs.com/mcp. It is a remote MCP server over Streamable HTTP with no authentication, which makes it a good first connector: nothing to sign in to and nothing to leak.

1. In Le Chat, open Intelligence → Connectors and select Add Connector. On Free, Pro and Student plans you are the admin. The Le Chat page has the Open Le Chat button.

2. Open the Custom MCP Connector tab, name it Kuchi, paste this URL and select Connect. Le Chat detects that no authentication is needed.

https://kuchi.kalarislabs.com/mcp

3. Turn the connector on in a chat and paste the setup prompt from this page.

Check that it works

Ask Le Chat to list the tools from the connector. It should see 13: eleven that start with kuchi_, plus search and fetch.

How a remote MCP connector works in Le Chat

A connector is a client for a server somewhere else. Le Chat connects to the URL over Streamable HTTP: each message is a JSON-RPC 2.0 request sent as an HTTP POST. On connect it asks the server what it is (initialize) and what it can do (tools/list). Each tool comes with a name, a description, a JSON Schema for its arguments and annotations that say whether it changes anything.

When you ask for something a tool can do, Le Chat writes the arguments, sends a tools/call, and reads the result back into the conversation. Results can be text, structured JSON and links to files, which is how a storyboard image or a video file arrives without being pasted into the chat.

What the connector can and cannot see

  • It sees only what Le Chat sends. A tool call carries the arguments Le Chat writes: your product description, the template you picked, your shot analysis. It does not see the rest of the chat, your files or your account.
  • Every tool is read-only. They are annotated readOnlyHint: true, destructiveHint: false, idempotentHint: true and openWorldHint: false: nothing on the server changes, repeated calls return the same answer, and no tool reaches the wider web.
  • No credentials. The server needs no sign-in, token or API key. If a connector you did not write asks for credentials it does not need, do not give them.
  • Nothing is kept from your plans. The server records anonymous usage (which tool ran, how long it took, whether it failed, the client's name), never the contents of your plan or check, and never your IP address. The privacy page has the details.
  • Data it returns is data. Catalog text describes videos; Le Chat should treat it as information, never as instructions. That is the right stance for every connector.

First thing to try: plan a launch video

Paste the setup prompt once, then work through these:

Setup prompt
Connect the Kuchi MCP server at https://kuchi.kalarislabs.com/mcp (Streamable HTTP, no sign-in) and confirm it works by listing its tools.

Kuchi is a library of real product-launch videos to use as inspiration templates. When I want a launch video, read kuchi_get_workflow and follow it: get a short list with kuchi_suggest_templates and show me each one's poster and link so I can choose, in chat or by picking a video on kuchi.kalarislabs.com and pasting its link. Once I pick one, study it with kuchi_get_breakdown, look at its storyboard and note what each shot shows, then call kuchi_plan_remake with my product details and your shot analysis, and ask me for my logo, screenshots and anything else it lists as missing. Build to the blueprint's frames. Before you deliver, run kuchi_check_remake and compare your frames with the reference. Copy only the reference's motion and taste; everything on screen comes from my product.
  1. Suggest launch video templates for a European fintech app and show each poster and link.
  2. Study my pick shot by shot.
  3. Plan my remake at 30 seconds, 16:9.
  4. Write the plan out for a coding agent.

Le Chat ends with a frame-timed blueprint: every shot with its start and end frame, how it enters and what of yours goes in it. A coding agent such as Claude Code or Codex builds and renders that blueprint in Remotion. The Le Chat launch video page has more prompts.

Common problems

  • The connector added but not turned on in the chat.
  • Team plans. An admin may need to add the connector for the organisation.
  • Pasting the website address instead of the /mcp URL.

Questions

How do I add a custom MCP connector to Le Chat?

Open Intelligence → Connectors, choose Add Connector, open the Custom MCP Connector tab, name it, paste the URL and connect.

Who can add connectors?

On Free, Pro and Student plans you can. On team plans, an admin.

Can Le Chat make the video?

It plans the video. A coding agent builds and renders it.