How to add a custom connector (remote MCP server) to Claude
Claude can use tools from any remote MCP server you add as a custom connector. Once added on claude.ai, the connector follows your account to the desktop app as well.
This guide adds one by URL, checks it, and puts it to work planning a product launch video from a real reference.
What a custom connector lets Claude do
- Search and read a library Claude has no other way to see.
- Call tools mid-conversation, with your approval the first time.
- Use the same connector on the web and in the desktop app.
- Pair with artifacts: Claude can lay the shot plan out as a table you keep.
Add a custom MCP server to Claude
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. On claude.ai, add Kuchi as a custom connector. The link fills in the name and URL. The Claude page has the Add connector button.
2. In the Claude desktop app, open a chat with the setup prompt filled in. The Claude page has the Open in Claude button.
3. Or add a custom connector by hand with this URL. No authentication.
https://kuchi.kalarislabs.com/mcpCheck that it works
Open a new chat, turn the connector on from the tools menu and ask Claude to list its tools. It should see 13: eleven that start with kuchi_, plus search and fetch.
How a remote MCP connector works in Claude
A connector is a client for a server somewhere else. Claude 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, Claude 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 Claude sends. A tool call carries the arguments Claude 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: trueandopenWorldHint: 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; Claude 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:
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.- Suggest three launch video templates for my product (describe it in a sentence) and show each poster and link.
- Study the one I pick: what does each shot show?
- Plan my remake at 30 seconds and list everything you need from me.
- Lay the final shot plan out as a table I can hand to a coding agent.
Claude 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 Claude launch video page has more prompts.
Common problems
- Connector added but off in the chat. Turn it on from the tools menu.
- Pasting the URL with a trailing space or without https.
- Expecting Claude to render the file. Claude plans; a coding agent such as Claude Code renders.
Questions
How do I add a custom connector to Claude?
Open Customize → Connectors on claude.ai, add a custom connector, give it a name and paste the server URL. Leave authentication empty for a server that needs none.
Do custom connectors work in the Claude desktop app?
Yes. A connector added to your account is available on claude.ai and in the desktop app.
Can Claude make the video itself?
Claude chooses the template, studies it and writes the frame-timed plan. Claude Code builds and renders it.

