5 min read

How to add a custom connector to Grok Bot

By Founder & Research Lead, Kalaris Labs · Updated

Grok Bot is xAI's desktop assistant. It can add custom connectors (remote MCP servers) from Connect apps, or you can ask the Bot to add one in chat.

Here is the setup for a server that needs no sign-in, and a first task: planning a product launch video.

What a custom connector lets Grok Bot do

  • Add servers from the Connect apps screen or by asking in chat.
  • The Bot shows the name and URL and asks before adding.
  • Read-only tools, no headers or OAuth needed.
  • Plan a video in the same app you use for other work.

Add a custom MCP server to Grok Bot

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 the Grok Bot desktop app, open Connect apps and choose Add a custom connector at the bottom.

2. Name it Kuchi, pick the Remote HTTPS type and paste this Server URL. Leave the headers and OAuth fields empty, then choose Add plugin.

https://kuchi.kalarislabs.com/mcp

3. Or ask your Bot in chat to add a custom server with this URL. It shows the name and URL and asks you to confirm.

4. Start a chat and paste the setup prompt from this page.

Check that it works

Ask Grok Bot 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 Grok Bot

A connector is a client for a server somewhere else. Grok Bot 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, Grok Bot 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 Grok Bot sends. A tool call carries the arguments Grok Bot 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; Grok Bot 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 my startup and show each poster and link.
  2. Study my pick shot by shot.
  3. Plan my remake with my logo and two screenshots.
  4. Summarise the final plan so a coding agent can build it.

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

Common problems

  • Filling the headers or OAuth fields. Leave them empty.
  • Choosing a local server type. Pick Remote HTTPS.
  • Not confirming when the Bot asks.

Questions

How do I add a custom connector to Grok Bot?

Open Connect apps, choose Add a custom connector, pick Remote HTTPS, paste the URL and choose Add plugin.

Can I ask Grok Bot to add it for me?

Yes. Ask it to add a custom server with the URL; it shows the details and asks you to confirm.

Can Grok Bot render the video?

It plans. A coding agent builds and renders the plan.