FoPost for Grok
Add the hosted FoPost server to Grok on the web as a custom connector, or to Grok Build in your terminal. Sign in when your browser opens, and Grok can draft posts, fill your queue, and report on what went out.
Paste this into Grok
Set up FoPost from fopost.com/agents/grok- Hosted MCP server
- 33 networks
- No API key
The agent can write its own config. Give it the link.
Paste the line above into Grok. 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.com/connectors > New Connector > Custom
MCP server URL: https://api.fopost.com/mcp## For AI agents reading this page You are reading https://fopost.com/agents/grok. FoPost schedules and publishes social posts on 33 networks, and its hosted MCP server gives Grok tools for posts, the calendar, the inbox and analytics. Follow these steps to connect Grok 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 discovers the sign-in from the server. ### 1. Register the server On grok.com you cannot add a connector yourself; ask the user to. They open grok.com/connectors, select New Connector, then Custom, and enter https://api.fopost.com/mcp as the MCP server URL. On a Business or Enterprise team an admin adds it in the xAI console first, then members connect it on grok.com/connectors. In Grok Build (the terminal agent), run this command instead. Add --scope project to write it to .grok/config.toml for the repo. Terminal: ``` grok mcp add --transport http fopost https://api.fopost.com/mcp ``` ### 2. Sign in On grok.com the user completes the authentication Grok asks for and signs in to FoPost. Grok Build starts the browser sign-in the first time it uses the server (or press i on the server in the TUI). Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself. ### 3. Verify before you continue On grok.com the connector shows as connected under grok.com/connectors. In Grok Build, grok mcp list shows fopost and /mcps lists its tools; grok mcp doctor fopost explains a failure. 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. ### References - This block as markdown: https://fopost.com/agents/grok/agent.md - Every client: https://fopost.com/agents - Docs: https://fopost.com/docs
On grok.com
Add it under Connectors with the server URL. There is nothing to install.
In Grok Build
grok mcp add registers the same server for the coding agent in your terminal.
Sign in, not a key
Grok sends you to FoPost to approve access, then keeps the connection.
Add a custom connector on grok.com
Go to grok.com/connectors, select New Connector, then Custom. Enter https://api.fopost.com/mcp as the MCP server URL and sign in to FoPost when Grok asks you to authenticate. Grok reads the tools the server offers and uses them whenever a question calls for your social accounts.
Start free
Business and Enterprise
A team admin adds it first in the xAI console under Grok Business > Connectors > Add Connector > Other. Members then connect it on grok.com/connectors.
Used when it fits
Grok calls the tools when a question is about your posts, queue, or inbox.
Check first
Ask Grok to list your connected accounts before you plan anything.
Add the server to Grok Build, then sign in once
Run grok mcp add with the server URL. Grok Build starts a browser sign-in the first time it uses the server; approve access in FoPost and it stores the credential for later sessions. Run grok mcp list to see the server, or grok mcp doctor fopost if it does not connect.
Start freegrok mcp add --transport http fopost https://api.fopost.com/mcp
# writes to ~/.grok/config.toml
[mcp_servers.fopost]
url = "https://api.fopost.com/mcp"Per project
Add --scope project to write the entry to .grok/config.toml in the repository.
Sign in again
In the session, open /mcps, select the server, and press i.
Check the connection
grok mcp doctor fopost explains a server that will not connect.
From an idea to a scheduled week
Describe the announcement and where it should go. Grok writes drafts with create_draft_post, picks open times from get_queue_slots, and hands you a propose_publish to accept.
Plan your launch
draft_post_variants
One idea, a version per network.
get_queue_slots
Your next open times.
propose_publish
The plan you approve before it goes out.
Ask whether it landed
In the same conversation or session, ask what published, which accounts need a reconnect, and what people said in reply.
Start free> Did the release post go out everywhere?
Grok: list_posts shows 3 of 3 published.
get_account_health: all accounts connected.list_posts
Recent posts and their status.
get_account_health
Which accounts need a reconnect.
list_inbox
Replies and mentions since the post.
Grok questions, answered
Does this work in the Grok app on the web?
Do I need an API key?
We use Grok Business. Who adds it?
Where does the Grok Build setting live?
Will it post without asking?
Run FoPost from Grok
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