How to integrate Composio MCP with Grok Build

Connect Grok Build to Composio MCP. Generate a step-by-step workflow plan, check active connections for all toolkits, and more from your terminal, with authentication handled for you.

Composio logoComposio
No Auth

Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed.

25 Tools

How to integrate Composio 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 Composio account to Grok Build through Composio, so it can generate a step-by-step workflow plan, check active connections for all toolkits, download public S3 file to local path, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Composio with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's Composio 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 Composio 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 Composio 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 Composio account through Composio. On the first Composio 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 Composio

  • Generate a step-by-step workflow plan
  • Check active connections for all toolkits
  • Download public S3 file to local path
  • Show tool dependencies for workflow setup

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Composio 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 Composio action and event your agent gets out of the box.

Check multiple active connections

Check active connection status for multiple toolkits or specific connected account ids.

Create Plan

This is a workflow builder that ensures the LLM produces a complete, step-by-step plan for any use case.

Download S3 File

Download a file from a public s3 (or r2) url to a local path.

Enable trigger

Enable a specific trigger for the authenticated user.

Execute Composio Tool

Execute a tool using the composio api.

Get Tool Dependency Graph

Get the dependency graph for a given tool, showing related parent tools that might be useful.

Get required parameters for connection

Gets the required parameters for connecting to a toolkit via initiate connection.

Get response schema

Retrieves the response schema for a specified composio tool.

Initiate connection

Initiate a connection to a toolkit with comprehensive authentication support.

List toolkits

List all the available toolkits on composio with filtering options.

List triggers

List available triggers and their configuration schemas.

Manage connections

Create or manage connections to user's apps.

Multi Execute Composio Tools

Fast and parallel tool executor for tools discovered through COMPOSIO_SEARCH_TOOLS.

Run bash commands

Execute bash commands in a REMOTE sandbox for file operations, data processing, and system tasks.

Execute Code remotely in work bench

Process **REMOTE FILES** or script BULK TOOL EXECUTIONS using Python code IN A REMOTE SANDBOX.

Search Composio Tools

Tool Server Info: Composio connects 500+ apps—Slack, GitHub, Notion, Google Workspace (Gmail, Sheets, Drive, Calendar), Microsoft (Outlook, Teams), X/Twitter, Figma, Web Search / Deep research, Browser tool (scrape URLs, browser automation), Meta apps (Instagram, Meta Ads), TikTok, AI tools like Nano Banana & Veo3, and more—for seamless cross-app automation.

Wait for connection

Wait for connections to be established for given toolkits.

Check active connection (deprecated)

Deprecated: use check active connections instead for bulk operations.

Create / Update Recipe from Workflow

Convert executed workflow into a reusable notebook.

Execute Recipe

Executes a Recipe

Create / Update Recipe from Workflow

Convert the executed workflow into a recipe using Python Pydantic code.

Get Recipe Details by Slug

Get the details of an existing recipe by its slug.

Get Existing Recipe Details

Get the details of the existing recipe for a given recipe id.

Wait for connection

Wait for user auth to finish.

Get Tool Schemas

Retrieve input schemas for tools by slug.

FAQ

Frequently asked questions

A standalone Composio MCP server gives Grok Build a fixed set of Composio tools tied to that one server. The Composio Tool Router lets Grok Build load tools from Composio 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 Composio data and credentials are handled to that standard.

Start with Composio.It takes 30 seconds.

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

Start building