Directory
Search, filter by tool or topic, sort, and save ideas in this browser.
Loading directory…
Tools
Topics
11matches
Official xAI guide: Share as Template packages instructions, skills, routines and first-party plugins into an anonymized blueprint (team or public link)—no secrets, custom code, MCP servers, logins or history. Installers get a fresh bot that must re-approve plugins; encode setup steps for API keys and custom MCP so others can reproduce the workflow.
Power users summarizing Oct Grok Bot shipments highlight durable consumer/builder patterns: forward mail to the bot’s own inbox for triage, Shopify connector for catalog/ops chores, Slack team bots for shared workflows, plus faster computer tasks and native X reads without API keys. Treat as a checklist of connectors to wire once you have a Grok Bot computer—not a single launch post.
Marc Lou’s MailCheap exposes Streamable HTTP MCP at https://mailcheap.ai/mcp so ChatGPT, Claude and Grok Bot connect with OAuth (no key to copy); Claude Code, Codex and Cursor use a bearer API key. Agents can draft campaigns, send tests, schedule issues and read stats; schedule/send tools are marked destructive and ask before sending. Open-source / self-host option; pay only for SES-style sends vs beehiiv-class plans.
MIT Go daemon + git hook reviews every commit with the CLIs you already pay for—Codex, Claude Code, Cursor, OpenCode, and first-class Grok Build (grok / grok-build). Findings stay in a ledger until closed; agent hooks push open review IDs back into the session for /roborev-fix before context goes cold. Reviews stay on your machine.
Skysay’s launch post positions agent-native telephony—real numbers, calls, SMS—as MCP tools described in llms.txt, with client recipes for Grok Bot and other assistants. Pattern for builders: expose billable / regulated actions as scoped MCP tools with read-only first, quotes before spend, and carrier-review gates per country.
Skysay’s hosted Streamable HTTP MCP (https://api.skysay.ai/mcp) lets Grok Bot check coverage, request numbers, place approved outbound calls through a hosted voice agent, and send SMS—OAuth/PKCE, separate call vs SMS approval, no local Twilio bridge. Start read-only with account_overview; outside US/CA/UK/MX outbound often needs carrier review first.
Lauren Tan’s dr eggbot (Grok Bot Marketplace featured + SpaceXAI team picks) is a meta-bot: describe the job, answer a few clarifying questions, and it designs a specialised Grok Bot for that lane. X users confirm starting with one request and ending with more bots than planned; watch usage—recursive bot-building loops can burn monthly limits fast.
Daniel Gartshein’s Haggle Bot (From Grok Bot Team on the marketplace) inventories SaaS spend from Ramp and bills, finds evidence-backed savings (unused seats, duplicates, cheaper alternatives), and drafts vendor counters for your review. Explicitly never spends, signs, or sends without you—useful ops desk for builders who want agent help on costs without auto-negotiation.
monokern (Oct 16) highlights that SpaceXAI’s own Grok Bot team published job-specific bot templates in the official marketplace (x.ai/bot/marketplace): import a setup built for one job, connect your tools, and adapt it. Roundup of 10 team picks includes dr eggbot (bot builder), Lingxi’s Engineer Bot (cloud agents + PR watch), Stalk Bot (competitor intel), Haggle Bot (SaaS spend), Proto Bot (idea→draft PR), Video Editor, figma bro, Distro Bot, Startup QA Bot, and Signal Prospector—each designed so nothing sends/merges without your yes.
Night Orders Studio’s Grok Bot Chief of Staff describes the same hybrid SpaceXAI ships: hand coding to Cursor cloud agents and a Grok Build terminal, while a desk of agents (Build, Legal, Tester, App Store) checks every build and one human signs off. Lingxi Li’s Engineer Bot on the Grok Bot Marketplace packages the supervisor lane—board work on the repo you name, launch cloud agents, watch PRs ~every 30 minutes, only ask you to merge.
Common xAI stack pattern (confirmed by @grok replies and power users): keep Grok Bot as the always-on teammate that plans, researchs, and hands off; route multi-file coding to Grok Build CLI (`curl -fsSL https://x.ai/cli/install.sh | bash`—plan mode, parallel subagents, skills) or Cursor cloud agents. Bot’s cloud computer can still clone/run code, but dedicated local/repo coding stays cheaper and more controlled on Build.