# Write social media posts directly in Grok Build

> Source: https://tareno.co/agents/grok-build
> Language: en
> Connect Tareno to Grok Build as a remote MCP server, turn a release or build log into X and LinkedIn drafts and approve every request in Tareno. Setup follows xAI's documentation.

Grok Build is xAI's terminal coding agent, and the source is published in xAI's own repository. It reads a repository, runs commands and, through MCP, talks to servers that you add. Add Tareno and the same session that wrote the change can draft the post about it and save that draft in your account. Tareno holds every scheduling and publishing request until you approve it. This page is about Grok Build, the terminal agent, and not about Grok Bot, which is a different product with its own guide. The setup follows xAI's documentation, and Tareno has not completed a client test with Grok Build.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | Grok Build (grok-build) |
| Available connection | Custom MCP connection |
| Connection evidence | documented |
| Methods | mcp |
| Authentication | oauth |
| Setup | [Setup guide](https://tareno.co/docs/mcp) |
| Install or connect | [Open setup](https://tareno.co/docs/mcp) |
| Evidence observed | 2026-10-25 |
| Facts reviewed | 2026-10-25 |

Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface.

## How do I connect Tareno to Grok Build?

Run the grok mcp add command with the http transport, a name such as tareno and Tareno's MCP address, or add the server under mcp_servers in ~/.grok/config.toml. Use the project scope only for servers without secrets. For OAuth, Grok opens a browser flow and stores the token. xAI documents the flow, and Tareno has not completed a client test.

## Connect Grok Build in four steps

1. **Choose where the server lives.** xAI's guide says grok mcp add writes to your user file at ~/.grok/config.toml by default, and writes to .grok/config.toml in the repository when you pass the project scope. A server without secrets can live in the project file and be committed; a personal sign-in belongs in the user file.
2. **Add Tareno as a remote server.** Pass the http transport, a name made of letters, numbers, hyphens or underscores, and the address shown on the right. xAI recommends this native URL form over wrapping a server in an npx mcp-remote proxy, because Grok then handles OAuth itself.
3. **Authenticate.** The guide says Grok opens a browser authorization flow when a server asks for OAuth, and you can also press i on the server in the /mcps screen. Tokens are stored as plaintext in ~/.grok/mcp_credentials.json with owner-only permissions, so keep that machine yours.
4. **Check what loaded.** grok inspect shows which servers are loaded and where they come from, and grok mcp doctor is the first diagnostic step. Then ask Grok Build to call `list_accounts`. Your account appearing in the answer is the confirmation; an empty answer means it has to be connected inside Tareno.

Tareno's remote MCP endpoint:

```json
"url": "https://tareno.co/api/mcp"
```

## Where Grok Build helps with Tareno

A terminal agent sits next to the work that people want to talk about. These jobs use that proximity, and each has a workflow guide.

### A release becomes an X post from the diff itself

Grok Build can read the commits and the changelog of a tagged release and write the post from what changed, not from memory. You read it against the diff, then it is saved as a draft, which is more reliable than writing the announcement an hour after the build when details have blurred.

### A finished project becomes a LinkedIn case study

When a migration or an optimization is done, the evidence is still in the repository: before and after numbers, the issue thread, the benchmark script. Grok Build can pull those into a LinkedIn draft with the limits stated, leaving you to remove anything private before it is saved.

### Compatibility with the tools you already use

xAI's guide says Grok also reads MCP definitions from ~/.claude.json, .cursor/mcp.json and a project .mcp.json, with config.toml taking priority. A team that already configured Tareno for another coding agent may find it picked up, which is convenient and worth checking with grok inspect.

## Prompts to copy

### Check the connection

```text
Use Tareno to list my connected social accounts with platform and account name. Read only: do not create, schedule or publish anything. Tell me which account you would use for a release post on X and which for a LinkedIn case study.
```

### Release post from the diff

```text
Read the commits between the last two tags and the CHANGELOG entry, then write an X post within 280 characters that states the one change users will notice most. List the commit hashes the claim rests on, and do not mention anything that is not in them.
```

### Case study with limits

```text
From the issue thread and the benchmark output in this repository, write a LinkedIn draft of about 200 words on the performance work, with the before and after numbers, the machine they were measured on and one limitation. Leave out file paths and customer names.
```

### Save the drafts

```text
Use Tareno to confirm my X account [handle] and my LinkedIn profile [name], then save the two approved texts as separate drafts. Return each draft ID with its text, and request no time until I give you the day and the time zone.
```

### Request the slots

```text
Take the drafts [draft IDs] and ask Tareno to schedule them for [Tuesday 09:00] in [America/Los_Angeles]. Return the action IDs and remind me that each request still waits for my approval in the Tareno dashboard.
```

## Guides by network

- LinkedIn: [Can Grok Build turn finished engineering work into a LinkedIn case study?](https://tareno.co/agents/grok-build/linkedin) ([Markdown](https://tareno.co/agents/grok-build/linkedin.md))
- X: [Can Grok Build write an X release post from the diff between two tags?](https://tareno.co/agents/grok-build/x) ([Markdown](https://tareno.co/agents/grok-build/x.md))

## Good to know before you start

- Tareno has not completed a client test with Grok Build. The steps follow xAI's documentation, so verify the connection with a read-only call before you rely on it.
- Grok Build and Grok Bot are different products. Their setup, config files and guides are separate, so use the page that matches the tool you run.
- Header values and OAuth tokens are stored as written or in plaintext files on your machine. Keep secrets out of a committed project config and reference environment variables instead.
- xAI's guide does not describe a general approval model for MCP tools, so treat Tareno's pending actions as the real gate before anything is published.
- Scheduling, publishing, edits to scheduled posts and deletions create approval actions in Tareno. Grok Build can request them but cannot approve them.

## Grok Build compared with other coding agents

Codex, Claude Code and Cursor reach Tareno through documented setups that Tareno knows well. Grok Build uses the same remote MCP idea with its own commands and config file, plus compatibility with other tools' definitions. If you already work with xAI's models, it keeps the announcement in the same session as the code. If not, choose the agent your team already uses.

## Frequently asked questions

### Is Grok Build the same as Grok Bot?

No. Grok Build is xAI's terminal coding agent, while Grok Bot is a separate product with a plugin and connector model of its own. Tareno has a separate guide for each, and the setup steps on one page do not apply to the other.

### Where does Grok Build keep its MCP settings?

In ~/.grok/config.toml for your user, and in .grok/config.toml inside a repository for project servers, according to xAI's guide. Project files are limited to MCP servers, plugins and permission rules, and secrets should not be written into a committed one.

### Does Grok Build handle OAuth for remote servers?

Yes, according to xAI's guide: when a server requests OAuth, Grok opens a browser authorization flow and stores the tokens. You authenticate once, and the stored credentials are reused, so sign in with your own Tareno account rather than a shared one.

### Has Tareno tested this connection?

Not yet. The setup follows xAI's published documentation and Tareno's OAuth is standard, but a full read-only run through Grok Build has not been completed. Run `list_accounts` first and treat the result as the test for your own setup.

### What does grok mcp doctor do?

xAI's guide names it as the first diagnostic step when a server does not load. Together with grok inspect, which shows loaded servers and where each one came from, it tells you whether a problem is in the config, the transport or the sign-in.

### Can Grok Build publish a post without my approval?

No. A scheduling or publishing request becomes an approval action in Tareno, and nothing reaches X or LinkedIn until you approve it in the dashboard. Grok Build can only report that the action is pending and read its status afterwards.

### Can I reuse a Claude Code or Cursor config?

Possibly. xAI's guide says Grok also reads ~/.claude.json, .cursor/mcp.json and a project .mcp.json, with its own config taking priority. Run grok inspect to see what it actually loaded, because a stale definition can point at an old address.

### Which Tareno tools will Grok Build call first?

Usually `list_accounts` to confirm the destination, then `create_drafts` to save the text. `schedule_posts` comes last and returns an approval action instead of publishing anything, and `get_action_status` tells you what became of the request.

## Tareno tools used

- `list_accounts`
- `create_drafts`
- `schedule_posts`
- `get_action_status`

Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them.

## Related

- [A release post on X from the diff](https://tareno.co/agents/grok-build/x)
- [A LinkedIn case study from the repository](https://tareno.co/agents/grok-build/linkedin)
- [Remote MCP setup](https://tareno.co/docs/mcp)
- [Grok Bot × Tareno](https://tareno.co/agents/grok-bot)
- [Codex × Tareno](https://tareno.co/agents/codex)
- [Approval workflows](https://tareno.co/features/approval-workflows)