How to integrate Heartbeat MCP with Grok Build

Connect Grok Build to Heartbeat MCP. List all upcoming heartbeat community events, post a message in #general channel, and more from your terminal, with authentication handled for you.

Heartbeat logoHeartbeat
Api Key

Heartbeat is a plug-and-play platform for building and managing online communities. It helps you organize users, channels, events, and discussions in one place.

7 Tools

How to integrate Heartbeat MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your Heartbeat account to Grok Build through Composio, so it can list all upcoming Heartbeat community events, post a message in #general channel, get member count for each Heartbeat channel, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Heartbeat with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Heartbeat integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,000+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the Heartbeat account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect Heartbeat to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your Heartbeat account through Composio. On the first Heartbeat action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting Heartbeat

  • List all upcoming Heartbeat community events
  • Post a message in #general channel
  • Get member count for each Heartbeat channel

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Heartbeat scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
TOOLS

Supported Tools

Every Heartbeat action and event your agent gets out of the box.

Get Events

Tool to retrieve event information from the community.

List channels

Tool to retrieve a paginated list of channels in the community.

List Groups

Tool to retrieve a paginated list of access groups in the community.

List Users

Tool to retrieve a paginated list of users in the Heartbeat community.

Reactivate User

Tool to reactivate a previously deleted user by email to allow them to access the community again.

Retrieve Group

Tool to retrieve a single group by its ID.

Retrieve User

Tool to retrieve a single user by their ID.

FAQ

Frequently asked questions

A standalone Heartbeat MCP server gives Grok Build a fixed set of Heartbeat tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Heartbeat and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your Heartbeat data and credentials are handled to that standard.

Start with Heartbeat.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Heartbeat tool your agent needs.Free to start.

Start building