Working with her in Grok Bot
Grok Bot is the cloud agent: named bots, memory, routines. Grok on grok.com is a different product. Connecting PostQueen at grok.com/connectors does not install her on Grok Bot. Tell the Bot to add the remote MCP server. What she brings into that chat is her 14 MCP tools. They list your channels, read what each platform accepts and schedule the posts. They do not delete a post or return analytics, so that work lives on the calendar at app.postqueen.ai or in thepostqueen CLI.
Set up
Your key lives in the app at app.postqueen.ai: open Settings → API Keys and click Reveal. Then, in a Grok Bot chat:mcp.json not syncing, and team allowlists:
Grok Bot MCP setup
Step by step, from the Bot chat to your first tool call
integrationList and hands back your accounts, you are connected.
For Grok on the web and phone, see Grok.
👑 A week planned from Grok Bot
You: Plan five posts across next week for X and LinkedIn and schedule them for 9am each day.
Grok Bot: Reading your channels and what each one accepts, then scheduling with PostQueen.
integrationList running…
integrationSchema running for x, linkedin…
integrationSchedulePostTool running…
5 posts scheduled across X and LinkedIn, Monday to Friday at 9:00 AM. Every one is on your calendar if you want to change the wording.Want an image with a post?
generateImageTool produces one. Not ready for one of them to publish? Ask for drafts, and the call carries type as draft instead of schedule.
Learn more
Grok Bot setup over MCP
Add the server in the Bot chat. Not grok.com/connectors.
Grok chat
Custom connector at grok.com/connectors
Grok Build
Terminal agent. grok mcp add, not the Bot.
MCP tools
All 14 tools Grok Bot gains once the server is on