Grok Bot is very good at the first half of a job. Ask it what people are saying about your launch, how a competitor priced their new plan, or how you would build a tracker for either, and you get a sharp answer in seconds. Then the chat ends, and the tracker you just designed together still does not exist anywhere.
This post is for people who use Grok Bot every day and keep hitting that wall. Grok supports custom connectors over MCP, and Server4Agent is an MCP server built for exactly this gap: it gives the assistant a real server to build on and a URL to hand back. Add it once, and "build me a tool for this" becomes a request Grok Bot can actually finish.
Quick answer
At grok.com/connectors, click New Connector, choose Custom, paste https://mcp.server4agent.com, and authorize with your Server4Agent account when Grok asks. There is no API key to copy. From then on Grok Bot can create a server, have Server4Agent's build agent write and start an app, and publish it at its own address on apps.server4agent.com. Everything starts private, and a budget cap you set limits what it can spend.
Key takeaways
- Grok's custom connectors speak MCP, so connecting Server4Agent is a paste and a sign-in, not an integration project.
- The connector lives on your Grok account, so every Grok Bot chat after setup can end in a working tool instead of a code block.
- Grok Bot stays the place you talk. Server4Agent is the builder and the host behind the conversation.
- New projects are private. You choose when a link opens and to whom: your team, anyone with a password, or everyone.
- Projects persist, so "add a filter to last week's tracker" edits the same app at the same URL.
Where the chat runs out
Grok Bot is unusually good at keeping up with what is happening right now. That makes it a natural place to notice that you need a tool: a page that tracks a launch, a watcher for a competitor's pricing, a dashboard for the numbers you keep asking it about.
What it cannot do on its own is leave anything running. The best it can offer is code in a reply plus setup instructions: find hosting, get a domain, keep a process alive, remember where you put it. The assistant did the thinking and you inherited the infrastructure. That is the gap we described in the missing deployment layer for AI agents, and it looks the same in every chat app.
A connector closes it. With a server attached, Grok Bot's answer to "make me a tracker" is a link, and the tracker keeps working after you close the tab.
Connect it once
The integrations page keeps the current steps for every app. Here is the Grok version, which takes about two minutes:
- Open grok.com/connectors, click New Connector, and choose Custom.
- Paste the Server4Agent address:
https://mcp.server4agent.com - Grok opens a Server4Agent page. Sign in if you need to, then click Authorize.
That is the whole setup. The connector belongs to your Grok account rather than to one conversation, so Grok Bot can use it in every chat from then on.
To check that it worked, start a new chat and ask: "Which Server4Agent tools can you use?" You should get a list that includes creating servers and projects, building, and deploying. Asking for the tool list is a more reliable check than asking whether the connector is switched on.
A note on plans: custom connectors may need a paid Grok plan, and on Business or Enterprise workspaces an admin may have to allow them first. If Custom is missing under New Connector, that is usually why. xAI's connector documentation has the current rules.
Your first request
Start with something small enough to finish in one go and real enough to prove the loop:
> Create a Server4Agent server, build a one-page site that says "Hello from Grok Bot" with today's date, publish it, and send me the link.
That one message exercises every step: provisioning, building, starting the app, and putting it online. A few minutes later Grok Bot replies with an address on apps.server4agent.com, and the page is there when you open it. The quickstart walks through the same loop one step at a time.
Then ask for something you actually need.
What happens behind the reply
You never have to think about tools, but it helps to know what Grok Bot is doing when it says it is working on something. The phrases you would naturally use map onto the tools the connector adds:
| You say | Grok Bot calls | What happens |
|---|---|---|
| "Set me up a server." | create_server | Provisions a small server that can hold a few projects. |
| "Build me a tracker for..." | create_project, then prompt | Creates a private project and hands your brief to the build agent, which plans, writes, installs, and starts the app. |
| "Is it done yet?" | get_run | Checks on the build until it finishes. |
| "Make the chart weekly instead." | prompt again | Picks the same conversation back up and changes the same app. |
| "Share it with my team." | update_project | Opens the link to signed-in members of your account, and nobody else. |
| "Put it online." | deploy | Checks the app is answering, makes it public, and returns the live URL. |
| "How much have I spent this month?" | get_usage | Reports spend against your plan and your cap. |
Grok Bot does not have to write the code itself. The build agent on the server does the heavy lifting, which keeps the chat short and keeps the result the same whichever assistant asked for it. The full tool list, with every parameter, is on the MCP docs page.
Tools worth asking Grok Bot for
The sweet spot is small, specific software: too small to ask a developer for, too useful to keep doing by hand. A few good first builds:
- A competitor pricing watcher. "Check these three pricing pages every morning, keep a history, and highlight anything that changed." The idea is covered in depth in URL monitoring made simple.
- A launch-day status page. "Check our site and API every minute during the launch and show green or red on one page." Like this uptime monitor walkthrough.
- A feedback board. "Give beta users a page to leave feedback, and give me a list I can sort by status." Like this customer feedback board.
- A weekly numbers page. "Every Monday I paste the same three numbers into a chat. Make a page I upload a CSV to that charts them." See the weekly metrics digest.
- A cleanup tool you reuse. "Turn this export cleanup into a tool: upload, clean, download." Like this CSV cleanup app.
One thing to keep straight: the tool Grok Bot ships runs on your Server4Agent server, not inside Grok. It does not see your chats or your feed. It works from what you build it to read: public pages, feeds, files you upload, or an API whose key you hand over once as a secret. Grok Bot is where you notice what you need. The tool is what keeps doing it while you are away.
What it looks like in practice
The growth lead at Northstar Labs has asked Grok Bot the same question every morning for two weeks: did any of our three competitors change their pricing? With the connector on, they ask one more time, differently:
> Build a tool that checks these three pricing pages every morning, saves a copy each day, and shows me what changed since yesterday. Keep it private for now.
Grok Bot creates a project on their server and passes the brief to the build agent. While the build runs, Grok Bot checks on it and reports progress in the chat. A few minutes later it says the watcher is built and running, and private. The growth lead replies "share it with my team", and Grok Bot switches the link to team access: anyone at Northstar Labs who signs in can open it, and nobody else can.
The next day: "Also flag when a plan gets renamed, not just when a price moves." Same chat, same project, same URL, one more build. Nobody on the team opened a code editor or a hosting console.
Guardrails that come with it
An assistant that can build and publish needs boundaries. These are on by default.
Private until you say so. Every new project starts private: built and running, but not reachable from the internet. Publishing is a separate, explicit step, and you pick the audience: your team only (sign-in required), anyone with a password, or everyone. The address stays the same as you widen the audience, so the link your team reviewed is the link that goes public. More in private by default and sharing a tool with your team, not the public.
A budget cap you set. Building and hosting draw from usage credits. Set a monthly cap in your dashboard; when spending reaches it, new work pauses until you raise it, and Grok Bot cannot raise it for you. The worst case of an experiment is a paused task, never a surprise invoice. The mechanics are in how credits and budget caps keep agent compute predictable.
A real workspace underneath. Every link is backed by actual files, build history, and logs. If a tool grows into something your team depends on, a developer can open the project and carry on where Grok Bot left off, or export it and take it elsewhere. Nothing is locked inside a chat transcript. The security page has the rest.
Using Grok Build too?
If you also work in the terminal, Grok Build connects to the same Server4Agent account with one command, and the integrations page has it. Projects belong to your account rather than to the app that created them, so Grok Build can pick up a tool Grok Bot started, and the other way around.
Start with one question you keep asking
Pick the question you ask Grok Bot every week, or the chore you still do by hand after it answers. Connect once at the integrations page, get early access, and make your next chat the one that ends in a link.
FAQ
Do I need an API key?
No. Grok signs you in to Server4Agent in the browser when you add the connector. API keys are for developer tools that cannot do that sign-in, and for the SDKs.
I don't see Custom under New Connector. Now what?
Custom connectors depend on your Grok plan, and team workspaces may need an admin to enable them. xAI's connector docs list the current rules. If you cannot add it, you can describe the tool in the Server4Agent dashboard instead and get the same result.
Grok Bot says it built something, but I can't open the link.
That is usually privacy working as intended: new projects are private. Ask Grok Bot to share it with your team, put it behind a password, or publish it.
Can Grok Bot change something it built last week?
Yes. Projects persist. Name the tool ("the pricing watcher") and say what should change. Grok Bot finds the project and the build agent edits it in place, at the same URL.
Does the tool stop when I close Grok?
No. It lives on your Server4Agent server, not in the chat, so closing the tab or the app does not touch it.
Related reading
- The non-technical guide to shipping real tools from chat
- The first tool you should ask your AI assistant to build
- OpenClaw + Server4Agent: your personal AI assistant can ship real tools now
- Why every AI agent should be able to return a URL