FoPost cho Grok

## 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