Connect Grok Bot to Adly: content created on your brand, posted to X and beyond

What Grok Bot is, and where Adly fits

Grok Bot is xAI’s agent, currently in beta. It is a different product from the Grok chatbot on grok.com and X: it runs on a persistent cloud computer with a browser, files and a terminal, and it can reach other services through connectors and MCP servers. Grok Build is xAI’s command line agent, and it uses MCP servers too.

Grok can plan a campaign and write around what is happening on X. Adly is the marketing studio it can call for the rest: designs built on your logo, colors and contact details, tips carousels, product ads and short videos, ad copy in Arabic or English, and publishing to the accounts you connected.

Adly runs its own MCP server, tied to your Adly account, your brands and your usage limit. Grok connects to it with two things: the server URL and your Adly MCP key.

Fields for Grok Bot

In Grok Bot’s settings, add a custom MCP server and enter these fields. Replace the placeholder with your own key.

Name: Adly
URL: https://getadly.com/mcp
Header: Authorization: Bearer YOUR_ADLY_MCP_KEY

The server must be reachable over the public internet, and Adly’s is. Nothing needs to run on your machine.

Command for Grok Build

Grok Build is xAI’s command line agent. This adds Adly as a remote MCP server and reads your key from an environment variable.

export ADLY_MCP_KEY="paste your key here"
grok mcp add --transport http adly https://getadly.com/mcp --header "Authorization: Bearer ${ADLY_MCP_KEY}"

Keep the key out of shared files and scripts. If it leaks, revoke it in Adly and generate a new one.

What happens when Grok calls Adly

Grok follows the same steps you would follow in the Adly app:

1. Pick the brand. It searches your brands and selects the one you mean.
2. Create a job. A design, a tips carousel, a design around a product photo or a video.
3. Wait for it. Designs take a short while and videos take longer. The agent checks the job until the result is ready, then shows it to you.
4. Approve the design. Or ask for an edit in plain words. After approval Adly writes the ad copy.
5. Approve the copy and publish. Post now or schedule for later, on the networks you choose.

Every job also appears in the Adly app, so you can step in there at any point.

Grok on the web, Grok Bot and Grok Build

xAI has three places where a connection can live, and they do not sign in the same way.

• Grok Bot. Takes a custom MCP server by name, URL and optional headers. Adly’s key goes in the Authorization header.
• Grok Build. The grok mcp add command accepts a remote server over HTTP with a header. That is the command on this page.
• The connectors page on grok.com. It is built around signing in with OAuth. Adly does not offer OAuth sign-in for Grok yet, so use Grok Bot or Grok Build for now.

Posting to X through Adly

Grok lives next to X, so X is usually the first place you want the post to go. Adly publishes to the X account you connected, on Solo and up: up to 4 images or a video, with the caption fitted to 280 characters. Links are removed from posts to X. The details are in the X scheduler guide.

Where Adly can publish

Adly publishes to five networks:

• Facebook: the Facebook Page you connected. Posts, carousels, videos and Stories.
• Instagram: business or creator accounts. Posts, carousels, videos and Stories.
• TikTok: the TikTok account you connected. Video posts and photo posts. Stories are not supported on TikTok.
• LinkedIn: your connected personal profile. Posts with a design, video or images.
• X: the X account you connected, on Solo and up. Links are removed from posts to X.

More detail in the social media scheduler guide.

Good to know before you connect

• The key is the access. Anyone holding the key can create content on your brands. Revoke it in Adly the moment you stop using the connection.
• Grok Bot is in beta. Its settings screens change, which is why this guide names the fields and not an exact menu path.
• This guide follows xAI’s documentation. We wrote this guide from the vendor’s own documentation and could not test every screen from our region. If a step looks different for you, write to [email protected] and we will update it.