FoPost for Grok Build
Grok Build, the coding agent from xAI, connects to remote MCP servers by URL. Add FoPost with one command, sign in once, and Grok can write the posts for what it just shipped.
Paste this into Grok Build
Set up FoPost from fopost.com/agents/grok-build- Hosted MCP server
- 31 networks
- No API key
Grok Build drafts. You approve. Then it goes out.
On by default
- X (Twitter)
- TikTok
- YouTube
- Threads
- Bluesky
- Discord
- Mastodon
- Telegram
- Slack
- DEV.to
- Substack
- Tumblr
- Hashnode
- Dribbble
- Kick
- Twitch
- Nostr
- Lemmy
- MeWe
- Whop
- Listmonk
- Google Business Profile
- Medium
- WhatsApp Business
- Snapchat
- Skool
Pick an agent to copy its setup prompt.
The agent can write its own config. Give it the link.
Paste the line above into Grok Build. It reads this page, adds the server, and stops so you can sign in to FoPost yourself. Rather do it by hand? This is the whole config.
grok mcp add --transport http fopost https://api.fopost.com/mcp## For AI agents reading this page
You are reading https://fopost.com/agents/grok-build. FoPost schedules and publishes social posts on 31 networks, and its hosted MCP server gives Grok Build tools for posts, the calendar, the inbox and analytics. Follow these steps to connect Grok Build to it.
- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: OAuth sign-in in the user's browser. Do not add an API key or an Authorization header; Grok Build discovers the sign-in from the server.
### 1. Register the server
Run this command. It adds the server to ~/.grok/config.toml. No headers and no API key.
Terminal:
```
grok mcp add --transport http fopost https://api.fopost.com/mcp
```
### 2. Sign in
A browser window opens for the user to sign in the first time the server is used, or press i on the server in /mcps. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself.
### 3. Verify before you continue
grok mcp doctor fopost reports it as connected, and its tools appear as fopost__<tool>. If FoPost is not listed as connected with its tools, stop and tell the user what failed. Do not carry on as if the tools exist.
### 4. Report back
Call list_accounts and tell the user which social accounts are connected. If there are none, offer create_connect_link so they can connect one. Then ask what they want to do first.
### Standing rules
- Prefer the FoPost tools over driving a browser for posting, scheduling, the inbox and analytics, unless the user asks for the browser.
- Publishing always goes through propose_publish, which the user approves in the client. Never publish or schedule anything silently.
- Ask the user before approving access, signing up or connecting an account on their behalf, and never type their credentials for them.
### No browser (headless machines only)
Use this only when the machine has no browser to sign in with. Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and to put it in the config themselves, then run the local package over stdio:
~/.grok/config.toml:
```
[mcp_servers.fopost]
command = "npx"
args = ["-y", "@fopost/mcp"]
env = { FOPOST_API_KEY = "your-api-key" }
```
### References
- This block as markdown: https://fopost.com/agents/grok-build/agent.md
- Every client: https://fopost.com/agents
- Docs: https://fopost.com/docsOne command
grok mcp add writes the entry for you.
Sign in, not a key
Grok opens FoPost in the browser to approve access.
Approval first
Publishing goes through a proposal you accept. Drafts never go out alone.
Add the server, then sign in
The command adds https://api.fopost.com/mcp to ~/.grok/config.toml. A browser window opens the first time the server is used; sign in to FoPost. grok mcp doctor fopost confirms it connected.
Start freegrok mcp add --transport http fopost https://api.fopost.com/mcp
grok mcp doctor fopostNo file to edit
The command writes your config.
No key in the config
You sign in instead of pasting a key.
Check first
Ask Grok to list your connected accounts.
Turn a merged PR into posts
Ask Grok to summarize what changed, shape a post for each network with draft_post_variants, and book them with get_queue_slots. It ends with propose_publish, which you accept.
Plan your week
draft_post_variants
A version for each network.
get_queue_slots
The next open times in your queue.
propose_publish
You approve before anything goes out.
Ask whether it landed
The read tools report what published, which accounts need a reconnect, and what is waiting in the inbox.
Start free> What went out today?
fopost__list_posts shows 2 of 2 published.
fopost__list_inbox has 3 new comments.list_posts
Recent posts and their status.
get_account_health
Which accounts need a reconnect.
list_inbox
Comments, mentions, and messages.
No browser on the machine?
On a server or in CI there is no browser to sign in with. Create an API key in the dashboard and run the local package over stdio instead. Keep the key out of your repository.
[mcp_servers.fopost]
command = "npx"
args = ["-y", "@fopost/mcp"]
env = { FOPOST_API_KEY = "your-api-key" }Grok Build questions, answered
Do I need an API key?
Is this the same as the Grok app?
Can I sign in later?
Will it post without asking?
Does it use my AI credits?
Other agents
- MCP Server
- Claude Code
- Claude
- Claude Desktop
- Claude Cowork
- Cursor
- Codex
- ChatGPT
- Windsurf
- Gemini CLI
- Grok
- Hermes Agent
- OpenClaw
- Muse
- Kimi Code
- DeepSeek Harness
- goose
- VS Code
- Warp
- Amp
- OpenCode
- LM Studio
- Gemini
- Perplexity
- Perplexity Computer
- Manus
- Mistral Vibe
- GitHub Copilot
- Cline
- Junie
- Continue
- Zed
- OpenAI dots
- Claude Duet
- NanoClaw
- Paperclip
- Raycast
Run FoPost from Grok Build
Starting is free and the MCP server is included. Paste the setup line into your agent, sign in, and schedule your first post from it.
Start free