Ship release posts to social media from Grok Build.

Grok Build already reads your repo. One command connects SociaHive, so release notes become scheduled posts without leaving the terminal.

https://www.sociahive.com/api/mcp

Grok Build and SociaHive at a glance

How it connects
grok mcp add, or an entry in ~/.grok/config.toml
Sign-in
OAuth in your browser, or an API key header for scripts
What you need
Grok Build sign-in or an xAI API key; SociaHive trial or paid plan
Best for
Developers who announce releases and changelogs
Not for
Running on a timer by itself: it has no built-in scheduler

Set it up in Grok Build.

Needs a SociaHive trial or paid plan.

Connect SociaHive to Grok Build

Your server address

https://www.sociahive.com/api/mcp

Grok Build

Grok Build, in your terminal

  1. 1

    Run grok mcp add --transport http sociahive followed by the server address.

  2. 2

    Start grok. A browser opens the first time SociaHive is used; sign in and approve.

  3. 3

    Run /mcps in Grok Build to check that sociahive is connected.

Then: Ask Grok Build “Which SociaHive accounts can you post to?”

Install in Grok Build

Command

Signs in with OAuth in your browser.

grok mcp add --transport http sociahive https://www.sociahive.com/api/mcp

Command with an API key

For scripts and machines without a browser. Make the key in SociaHive under Settings → API keys.

export SOCIAHIVE_API_KEY=sk_your-api-key
grok mcp add --transport http sociahive https://www.sociahive.com/api/mcp \
  --header "Authorization: Bearer ${SOCIAHIVE_API_KEY}"

config.toml

Or add it by hand to ~/.grok/config.toml (or .grok/config.toml for one project).

[mcp_servers.sociahive]
url = "https://www.sociahive.com/api/mcp"
headers = { "Authorization" = "Bearer ${SOCIAHIVE_API_KEY}" }

Things to ask first.

Copy one into a chat once you are connected.

  • One post per release, queued on consecutive days.

  • All the launch posts shift together, nothing else moves.

  • SociaHive asks you to confirm, then it goes out.

What is Grok Build?

Grok Build is xAI’s coding agent. You use it as a full-screen app in the terminal, headless in scripts with grok -p, or inside other editors. It supports skills, plugins and MCP servers.

It is made by xAI and is separate from the Grok chat assistant and from Grok Bot, xAI’s always-on cloud agent. Grok Build runs on your machine and works on the code in front of it.

Connecting SociaHive lets Grok Build finish the announcement along with the code: it reads what changed, writes the posts and schedules them, and SociaHive publishes them through its queue.

Can Grok Build post on a schedule?

Not by itself. We have not seen xAI document a scheduler in Grok Build. Its headless mode, grok -p with a prompt, can be run by cron or your CI on a schedule you set.

You rarely need that for posting. Grok Build can schedule a whole week in one session, and SociaHive publishes each post at its time with your terminal closed.

Everything Grok Build can do in SociaHive.

Schedule posts

Write a post and queue it at your best time, on any account you connected.

Post right now

Publishes straight away, after you confirm in the chat.

See your calendar

Everything that is scheduled, across all your accounts.

Read your numbers

Reach, saves and engagement per post, and what to post more of.

Build DM automations

Describe it in one sentence. It builds the flow as a draft for you to turn on.

Check your automations

Which flows are live and how often each one fires.

Reuse what works

Save your best posts to an evergreen queue and reshare them later.

Move posts in bulk

Shift a whole day of posts in one go, keeping their times.

What Grok Build gets: the SociaHive MCP server.

One address, https://www.sociahive.com/api/mcp. The same server works in every AI tool on this site.

MCP (Model Context Protocol) is the open standard AI tools use to reach outside apps. SociaHive runs a hosted MCP server, so there is nothing to install or keep running: Grok Build calls it over the internet and acts in your SociaHive account. These are the tools it uses most. See every tool and the API.

ToolWhat it does
list_accountsLists the social accounts you connected to SociaHive.
create_scheduled_postWrites a post, with text, images or video, for one or more accounts.
schedule_postQueues a post at a time you pick or at your best time.
find_next_slotFinds the next free slot in your posting schedule.
publish_post_nowPublishes straight away, after you confirm.
upload_media_from_urlCopies an image or video from a public link into your media.
get_scheduler_calendarShows what is scheduled, across all accounts.
get_post_analyticsReads reach, likes, comments and saves per post.
get_content_insightsFinds which formats and topics beat your usual numbers.
generate_flowBuilds a DM automation from one sentence, as a draft.
list_flows_with_statsLists your automations, which are live and how often they run.
bulk_reschedule_postsMoves many scheduled posts in one go.

One connection, every channel.

Connect each account once in SociaHive and Grok Build can post to it. Scheduling covers 22 platforms; X needs a paid plan.

DM automations run on Instagram, Facebook, Messenger and WhatsApp on every paid plan, and on Telegram on Pro and Agency.

Is it safe to let Grok Build post for you?

  • You approve the connection

    Sign in to SociaHive and approve, or use an API key you can delete at any time. The agent never sees your social passwords.

  • Read-only if you want

    Tick “Read-only access” when you connect and the agent can look at everything and change nothing.

  • Nothing goes live by surprise

    Publishing right now asks for your yes in the chat. Automations it builds start as drafts until you turn them on.

  • Revoke in one click

    Settings → Connected apps in SociaHive cuts the agent off on its next request. API keys are deleted under Settings → API keys.

OAuth tokens are stored in ~/.grok/mcp_credentials.json on your machine. With an API key, keep it in an environment variable rather than in a config file you commit.

Grok Build or another AI tool?

Every one of them connects to the same SociaHive account.

AgentKindHow it connectsBest for
Grok BuildCoding agentgrok mcp add, or an entry in ~/.grok/config.tomlDevelopers who announce releases and changelogs
Claude CodeCoding agentThe SociaHive plugin, or claude mcp add with the server addressBulk work from files: CSVs, changelogs, release notes
CursorCoding agentThe Add to Cursor link, or mcp.json with the server addressAnnouncing what you ship without leaving the editor
CodexCoding agentcodex mcp add, or an [mcp_servers] entry in config.tomlTurning releases and diffs into posts
ChatGPTChat assistantA custom MCP plugin on chatgpt.com, with the SociaHive server addressWriting captions and scheduling them in the same chat
OpenAI dotsAutonomous agentCustom MCP server added in ChatGPT, then allowed for the dotWatching your calendar and automations between check-ins

What does it cost?

xAI’s docs describe signing in with your browser on first launch, or using an XAI_API_KEY billed through the xAI API. Check x.ai for which Grok plans include Grok Build.

On SociaHive, MCP access is part of the 7-day trial and every paid plan, from Creator up. There is no extra charge per tool call. See plans.

Included in the trial.

And on every paid plan. 7-day free trial for the paid features. No credit card required.

Connect Grok Build

Troubleshooting Grok Build.

Grok Build does not list sociahive.
Run grok mcp doctor. If you added it with --scope project, start grok from that project folder.
The browser sign-in never opens on a server or in CI.
Use the API key command instead, with SOCIAHIVE_API_KEY set in the environment.
Grok Build gives up on sociahive at startup on a slow network.
It waits 30 seconds for a server by default. Raise startup_timeout_sec under [mcp_servers.sociahive] in config.toml.
It asks me to upgrade
MCP access is part of the SociaHive trial and every paid plan. On the free plan the agent can connect, but each request answers with an upgrade link.
An account is missing
The agent only sees accounts connected in SociaHive. Connect it under Connected accounts, then ask the agent to list your accounts again.
A post did not go out
Ask the agent for the post’s status, or open it in SociaHive. A failed post shows the platform’s reason, for example an expired login that needs reconnecting.
It says it is not allowed to change anything
You connected with read-only access. Remove SociaHive under Settings → Connected apps and connect again without ticking it.

FAQ

Is Grok Build the same as Grok Bot or the Grok chatbot?

No. Grok Build is a coding agent you run yourself. Grok Bot is an always-on agent in xAI’s cloud, and Grok at grok.com is a chat assistant. Each connects to SociaHive in its own way.

Do I need an API key?

Not on your own computer: Grok Build signs in to SociaHive with OAuth in your browser. Use an API key for scripts, CI or servers with no browser.

Can I post from a script or a cron job?

Yes. Run grok -p with your request from cron or CI, using the API key setup. Ask it to schedule posts rather than publish them right away, since publishing now waits for a confirmation.

Does Grok Build pick up a server I added in another tool?

xAI says it also reads MCP settings from ~/.claude.json, .cursor/mcp.json and .mcp.json, so SociaHive may already be there. Check with grok mcp doctor.

Can it attach images from my repo?

SociaHive takes images by public link. Push the image somewhere public first, or upload it with the sociahive CLI, then ask Grok Build to use it.

Can it post or change things without asking me?

Automations it builds start as drafts, with every step written out, until they are turned on. Publishing a post right away needs your yes in the chat. If you only want it to look, tick “Read-only access” when you connect: it can read everything and change nothing.

Which plans include it?

The 7-day trial and every paid plan. On the free plan your assistant can still connect, but each request answers with a link to upgrade instead of running.

How do I disconnect it?

Open Settings → Connected apps in SociaHive and revoke it. It is cut off on its very next request. You can also remove the connector in your assistant.

Use SociaHive with other AI agents.