How to integrate RunPod MCP with Grok Build

Connect Grok Build to RunPod MCP. Launch a new gpu pod for inference, get status of all active pods, and more from your terminal, with authentication handled for you.

Get started for freeGet a demo
RunPod logoRunPod
Api Key

RunPod is a GPU cloud platform designed for AI and machine learning workloads. Instantly access scalable compute power for demanding AI tasks.

13 Tools

How to integrate RunPod 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 RunPod account to Grok Build through Composio, so it can launch a new GPU pod for inference, get status of all active pods, stop a running pod with ID 12345, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate RunPod with

ChatGPT WorkAntigravityOpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexCursorVS CodeOpenCodeOpenClawHermesGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

Why use Composio over a standalone MCP server?

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

  • Launch a new GPU pod for inference
  • Get status of all active pods
  • Stop a running pod with ID 12345

Security + privacy notes (important)

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

Create RunPod Cluster

Tool to create a new GPU cluster for multi-node distributed computing workloads on RunPod.

Create Secret

Tool to create a new secure secret in RunPod for credential management.

Delete Container Registry Authentication

Tool to delete container registry authentication from RunPod.

Delete Template

Tool to remove a RunPod template via GraphQL mutation.

Get GPU Types

Tool to retrieve available GPU types and their specifications, pricing, and availability from RunPod.

Get authenticated user info

Retrieve basic information about the authenticated user including ID, email, and security settings.

Get Pod Details

Retrieve details of a specific RunPod pod by its unique pod ID.

List CPU Types

Tool to retrieve available CPU types and their specifications from RunPod.

Save Serverless Endpoint

Tool to create or update a RunPod serverless endpoint with GPU configuration and scaling settings.

Save Container Registry Authentication

Tool to save container registry authentication credentials for accessing private Docker images in RunPod.

Save Template

Tool to create a new RunPod template or update an existing one with container configuration.

Update Registry Auth

Tool to update existing container registry authentication credentials in RunPod.

Update User Settings

Tool to update current user settings (e.

FRAMEWORKS

How to build RunPod MCP Agent with another framework

ChatGPT Work logo

ChatGPT Work

Use RunPod MCP with ChatGPT Work

Antigravity logo

Antigravity

Use RunPod MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use RunPod MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use RunPod MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use RunPod MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use RunPod MCP with Claude Cowork

Codex logo

Codex

Use RunPod MCP with Codex

Cursor logo

Cursor

Use RunPod MCP with Cursor

VS Code logo

VS Code

Use RunPod MCP with VS Code

OpenCode logo

OpenCode

Use RunPod MCP with OpenCode

OpenClaw logo

OpenClaw

Use RunPod MCP with OpenClaw

Hermes logo

Hermes

Use RunPod MCP with Hermes

Google ADK logo

Google ADK

Use RunPod MCP with Google ADK

LangChain logo

LangChain

Use RunPod MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use RunPod MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use RunPod MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use RunPod MCP with LlamaIndex

CrewAI logo

CrewAI

Use RunPod MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use RunPod MCP with Pydantic AI

AutoGen logo

AutoGen

Use RunPod MCP with AutoGen

FAQ

Frequently asked questions

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

Start with RunPod.It takes 30 seconds.

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

Start building