How to add a custom connector to Grok
Grok can use tools from a custom connector: a remote MCP server you add by URL. The setting is on the Connectors page.
This guide adds one that needs no sign-in, checks it, and uses it to plan a product launch video from a real reference.
What a custom connector lets Grok do
- Search and read a library Grok has no other access to.
- Get exact shot timings from measured videos.
- Use the tools in any Grok chat once connected.
- Read-only tools, nothing to sign in to.
Add a custom MCP server to Grok
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. Sign in to Grok and open Connectors. Select New Connector → Custom. The Grok page has the Open Connectors button.
2. Paste this URL. No sign-in is needed.
https://kuchi.kalarislabs.com/mcp3. Start a chat and paste the setup prompt from this page.
Check that it works
Ask Grok 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
A connector is a client for a server somewhere else. Grok 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 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 sends. A tool call carries the arguments Grok 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; Grok 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 launch video templates for a consumer app and show each poster and link.
- Study my pick shot by shot.
- Plan my remake for X, 16:9, 20 seconds.
- Write the plan out so Grok Build can build it.
Grok 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 launch video page has more prompts.
Common problems
- Not signed in. Connectors need a Grok account.
- Confusing Grok and Grok Build. The chat app plans; Grok Build writes and renders.
- The connector off in the chat.
Questions
How do I add a custom connector to Grok?
Open Connectors on grok.com, choose New Connector → Custom and paste the server URL.
Can Grok make the video?
Grok chooses, studies and plans. Grok Build or another coding agent builds and renders.
Does it work in the Grok Bot app too?
Grok Bot has its own connector setting; see the Grok Bot guide.

