How to integrate Nango MCP with Grok Build

Connect Grok Build to Nango MCP. List all connected crm accounts, trigger manual sync with salesforce provider, and more from your terminal, with authentication handled for you.

Get started for freeGet a demo
Nango logoNango
Api Key

Nango is a unified API platform that connects to 250+ SaaS apps across CRM, HR, and accounting. Streamline integrations with one API and simplify data sync across your business tools.

24 Tools

How to integrate Nango 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 Nango account to Grok Build through Composio, so it can list all connected CRM accounts, trigger manual sync with Salesforce provider, get configuration for all available scripts, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Nango 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 Nango 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 Nango 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 Nango 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 Nango account through Composio. On the first Nango 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 Nango

  • List all connected CRM accounts
  • Trigger manual sync with Salesforce provider
  • Get configuration for all available scripts
  • Show provider details for QuickBooks integration

Security + privacy notes (important)

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

Trigger Nango Action

Trigger a Nango action to execute a workflow or operation.

Add Connection

Tool to add a connection with existing credentials to Nango.

List Connections

List all Nango connections without credentials.

Create Connect Session

Tool to create a new connect session with a 30-minute lifespan for enabling connection creation via Connect UI.

Create Integration

Tool to create a new integration in Nango.

Delete Connection

Tool to delete a specific Nango connection.

Delete Integration

Tool to delete a specific integration by its unique key.

Edit Connection

Tool to edit a connection's tags and metadata.

Get Connection with Credentials

Retrieve a specific connection with its credentials.

Get Environment Variables

Tool to retrieve environment variables from the Nango dashboard.

Get Integration

Retrieve detailed configuration for a specific Nango integration by its unique key.

Proxy GET Request

Tool to make a GET request with Nango's Proxy to forward requests to external APIs while managing authentication.

Get Sync Status

Tool to get the status of specified sync(s) for a connection or all connections.

List Connections

Tool to list all connections without credentials.

List Integrations

Tool to retrieve a list of all configured integrations.

Get Provider Details

Retrieve detailed configuration for a specific Nango provider by its unique key.

List Providers

Tool to retrieve a list of all available providers.

Proxy PUT Request

Tool to make a PUT request with the Nango Proxy to forward requests to external APIs while managing authentication.

Reconnect Session

Create a new connect session to reconnect to a specific integration.

Get Integration Functions Configuration

Retrieve all integration functions configuration from Nango.

Set Connection Metadata

Tool to set custom metadata for one or more Nango connections.

Trigger Sync

Tool to trigger sync process(es) manually.

Update Connection Metadata

Tool to edit custom metadata for one or multiple connections.

Update Integration

Tool to update an existing integration's configuration.

FRAMEWORKS

How to build Nango MCP Agent with another framework

ChatGPT Work logo

ChatGPT Work

Use Nango MCP with ChatGPT Work

Antigravity logo

Antigravity

Use Nango MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Nango MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Nango MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Nango MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Nango MCP with Claude Cowork

Codex logo

Codex

Use Nango MCP with Codex

Cursor logo

Cursor

Use Nango MCP with Cursor

VS Code logo

VS Code

Use Nango MCP with VS Code

OpenCode logo

OpenCode

Use Nango MCP with OpenCode

OpenClaw logo

OpenClaw

Use Nango MCP with OpenClaw

Hermes logo

Hermes

Use Nango MCP with Hermes

Google ADK logo

Google ADK

Use Nango MCP with Google ADK

LangChain logo

LangChain

Use Nango MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Nango MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Nango MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Nango MCP with LlamaIndex

CrewAI logo

CrewAI

Use Nango MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Nango MCP with Pydantic AI

AutoGen logo

AutoGen

Use Nango MCP with AutoGen

FAQ

Frequently asked questions

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

Start with Nango.It takes 30 seconds.

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

Start building