Agent guides

Use AfterLaunch with Grok Bot

Grok Bot, from xAI, is an always-on agent: it works on its own schedule and comes back with results. Add AfterLaunch through its connector form, give it the standing orders, and each morning it brings you one growth decision with the evidence. After your yes it does the work and brings back the draft.

Connect

Add it through Connect apps, then Add a custom connector, in your Grok Bot app.

Server URL: https://afterlaunch.io/api/mcp
Authorization: Bearer YOUR_AFTERLAUNCH_API_KEY
  1. Create a key in AfterLaunch under API access on Connect your AI, set to Never expires, and keep it for Grok Bot alone.
  2. In your Grok Bot app open Connect apps, choose Add a custom connector, then Remote HTTPS, and name it AfterLaunch.
  3. Paste the server URL: https://afterlaunch.io/api/mcp
  4. Add one header: the name Authorization, and as its value the word Bearer, a space, then your key. Press Add plugin.
  5. Ask it to call the AfterLaunch whoami tool. It names your product.

Make a separate key for Grok Bot so you can revoke it on its own, under API access on Connect your AI. A key with Never expires matters here, because a Bot nobody is watching stops silently when a 90-day key runs out. To give it its orders, paste the standing orders from /agents/always-on.md into a chat and ask it to save them as a skill, then ask it to create a Routine for the morning check. Grok Bot needs a paid plan from xAI; check which on xAI's pricing page, docs.x.ai/x-subscription/pricing.

No key yet? Read the agents page or hand your agent /llms.txt, and it can run the onboarding flow: it submits your site and email, you approve with one click by email, and nothing runs until you do.

What Grok Bot can do

The 58 tools are the same whichever agent calls them. Once connected, Grok Bot can:

  • Read your ranked moves as a compact list, then use get_move for one move’s full material. Read the product run, its automated loops and drafted outputs too. All read-only and free.
  • Act on a move: record its confirmed completion, skip it with structured feedback, redraft the body before it goes out, or archive it. Free, on the act scope every self-serve key carries. Shipping stays the founder's decision; reporting it back the moment the work is live is the agent's, and it is what the engine measures the next ranking against.
  • Run the engine on demand: refresh an AI Visibility scan or top up your growth moves. These spend money, so they run on the write scope every key already carries and are metered: charged once per logical event, replayed on a repeat, and capped per tenant per day and per month.
  • Choose the questions you are measured on: track or untrack a customer question in the AI Visibility set. Both need the config scope and Founder tier.
  • Mint a Founder checkout link when the founder wants to upgrade. The link is always bound to the product run the key owns.
  • Write the Growth section into the repository it works in, the same block shown below, so the setup teaches the next session too.

Good to know for Grok Bot

  • What you need: a paid plan from xAI that includes Grok Bot (check which on xAI's pricing page, docs.x.ai/x-subscription/pricing), and an AfterLaunch account with a key. The free scan creates the account.
  • Give it its orders: paste the standing orders from /agents/always-on.md into a chat and say: save these as your standing orders and run them now. Ask it to save them as a skill in its skill library.
  • Then ask it to set its own Routine for the morning check, for example every day around 8:00 AM, with the Monday review folded in.
  • Revoke the key under API access on Connect your AI whenever you like. A separate key for Grok Bot means you can revoke it without touching any other agent.

Honest posture

Grok Bot runs the tools from its own app, not from your codebase, so there is no repository file. The standing orders live as a skill in its skill library, and they tell it never to post, publish, send or pay without your yes.

The AfterLaunch MCP server is remote and bearer-authenticated. There is no local process to install and nothing to execute on your machine: a config only points the agent at an HTTPS endpoint and attaches your key.

A key you mint yourself, or one an agent obtains through onboarding, carries the read, act and write scopes. Reading your growth moves and shipping, skipping, redrafting or archiving moves work straight away. The metered pulls run on that same write scope, bounded by the product run credits and the per-tenant caps, and changing the tracked questions needs the config scope and Founder tier.

AfterLaunch drafts. A human approves and posts. It never claims to have posted to a social channel on its own.

Reporting back is part of the loop, not an extra step. When the founder confirms a move is live the agent reads get_move for its current state, then calls ship_move to record that confirmation and its actual public URL when it knows it. Without one, AfterLaunch takes the address the move already holds; a change to a site the founder owns with no address held is recorded as prepared. A merged change goes with its page address as planned_url: AfterLaunch checks the page and marks it shipped once the text is live. Nobody is asked to paste a link. This records completion; it does not publish the work. When they decide against it the agent calls skip_move with the real reason. AfterLaunch measures what happens after a move ships, so an unreported ship is work the record never sees.

Questions

How do I add AfterLaunch to Grok Bot?

In your Grok Bot app open Connect apps, choose Add a custom connector, then Remote HTTPS. Name it AfterLaunch, paste https://afterlaunch.io/api/mcp as the server URL, add an Authorization header whose value is the word Bearer, a space and your AfterLaunch key, and press Add plugin.

Does Grok Bot publish anything on its own through AfterLaunch?

No. The standing orders tell it never to post, publish, send or pay without your yes, and no AfterLaunch key can publish to your channels.

Is AfterLaunch a growth marketing MCP server?

Yes, though the server is the door rather than the product. AfterLaunch is the agentic growth engine: it watches how the leading AI search engines answer about you, audits every page of your site, tracks your competitors and the communities and directories that decide whether you get found, and keeps the history. The remote MCP server at https://afterlaunch.io/api/mcp speaks Streamable HTTP and exposes 58 tools, so an agent reads your ranked growth moves, ships or redrafts them, and reads the product run, its automated loops and its drafted outputs. Reads are free. The on-demand runs are metered and capped per tenant per day and per month.

Can I use it as an SEO MCP server or an AI visibility MCP?

The same server exposes get_seo, the site-wide SEO audit with search ranks, links and ready-to-apply fixes, and get_visibility, how ChatGPT, Gemini, Perplexity and Google AI Overviews answer questions about your product, with share of mentions and cited sources. Both reads are free and need only a valid key.

Teach Grok Bot to use it

Grok Bot works from a chat rather than a repository, so there is no instructions file to write and nothing to install. The connector above is the whole setup. If you also work in a terminal or an editor, the guides below add the Growth section to that repository, so both surfaces reach for the same tools.

Or read the Growth section in your browser.

Using a different client?

Browse all agent guides, see the agents overview, or run a free growth tool first.