5 min read

How to add a custom MCP server to Manus

By Founder & Research Lead, Kalaris Labs · Updated

Manus is an agent that works through long tasks on its own. A custom MCP server gives it tools it would not otherwise have, and Manus tests the connection when you add one.

This guide adds a free launch video library and hands Manus a task: research and plan a product launch video from a real reference.

What a custom connector lets Manus do

  • Add a server by URL; Manus tests it and lists the tools.
  • Good at multi-step research: compare several templates before recommending one.
  • Read-only tools, nothing to authorise.
  • Hands you a plan a coding agent can build.

Add a custom MCP server to Manus

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 Manus, open Settings → Integrations → Custom MCP Servers and select Add Server. (In the Connectors view this is Create → Add MCP by URL.)

2. Name it Kuchi and paste this Server URL. Leave authentication empty. Manus tests the connection and lists the tools.

https://kuchi.kalarislabs.com/mcp

3. Start a task and paste the setup prompt from this page.

Check that it works

After you add the server, Manus tests the connection and lists the tools. You should see 13: eleven that start with kuchi_, plus search and fetch.

How a remote MCP connector works in Manus

A connector is a client for a server somewhere else. Manus 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, Manus 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 Manus sends. A tool call carries the arguments Manus 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; Manus 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. Find five launch video templates that fit my product, compare them and recommend one. Show posters and links.
  2. Study the one I pick and describe each shot.
  3. Plan my remake with my assets and list what is missing.
  4. Deliver the plan as a document I can give a coding agent.

Manus 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 Manus launch video page has more prompts.

Common problems

  • Filling the authentication field. Leave it empty.
  • Letting Manus pick the template on its own. Ask it to recommend and wait.
  • Expecting a rendered file. Use the plan with a coding agent.

Questions

How do I add a custom MCP server to Manus?

Open Settings → Integrations → Custom MCP Servers, choose Add Server, name it and paste the URL. In the Connectors view it is Create → Add MCP by URL.

Does Manus check the server?

Yes. It tests the connection and lists the server's tools.

Can Manus make the video?

Use it to choose and plan; a coding agent builds and renders the plan.