Grok Bot drafts the GTM plan, blog post, or social thread. Put the founder, content, and sales on one live link. When someone needs a change, agent connect hands it back to Grok Bot through MCP.
What people write with Grok Bot
Pick a doc type to see who reviews it, and what agent connect changes.
How it works
Author writes, reviewer comments, Grok Bot acts. The same hosted link covers the whole loop, before the file ever sees the CMS or the calendar.
October launch for a decaf subscription. Do not claim we are fresher than supermarket decaf. Week one is the subscriber email only.
Retail cards and the social thread move to week three, after the email is out.
Grok Bot writes markdown. Gander watches.
Reviewer opens the link. No install. Inline threads on the live doc.
Cut week one to the subscriber email and moved other channels to week three.
Week one is now the subscriber email. Other channels moved to week three. Leaving this open so you can check the month.
Agent connect comments reach Grok Bot through MCP. Grok Bot edits the file. The same link refreshes.
Install
The same install works on macOS and Linux. Windows users should use WSL.
$ curl -fsSL https://release.gander.md/install.sh | bash
$ gander signup --email [email protected]
$ gander mcp install
$ gander watch --silent plans/gtm-plan.mdOr: install the Gander skill and let the agent save the plan, watch the file, and poll for review. Skill docs.
Homebrew, flags, and other options: Install docs.
Add Gander as an MCP server for Grok Bot: command gander, args mcp. Then ask Grok Bot which Gander tools it has. You want gander_list_comments, gander_reply_comment, gander_resolve_thread, and gander_unresolve_thread.
No MCP connection? Run gander comments plans/gtm-plan.md and paste the agent connect threads back into the chat.
Step-by-step setup: Grok Bot docs. Every agent: Use with your agent.
Using a different agent? Other agents.
cut this to one channel for week one.