How to integrate Context7 MCP with Grok Build

Connect Grok Build to Context7 MCP. Get documentation for requests.get in python 3.11, show code example for async file read in node.js, and more from your terminal, with authentication handled for you.

Get started for freeGet a demo
Context7 MCP logoContext7 MCP
Api Key

Context7 MCP delivers live, version-specific code docs and examples right from the source. It helps developers and AI agents instantly retrieve authoritative programming info—no more out-of-date docs.

How to integrate Context7 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 Context7 account to Grok Build through Composio, so it can get documentation for requests.get in Python 3.11, show code example for async file read in Node.js, explain the difference between map and filter in JavaScript, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate Context7 MCP with

ChatGPT WorkAntigravityOpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexKimi CodeOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

Why use Composio over a standalone MCP server?

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

  • Get documentation for requests.get in Python 3.11
  • Show code example for async file read in Node.js
  • Explain the difference between map and filter in JavaScript

Security + privacy notes (important)

  • Use least-privilege access. Grant only the Context7 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.
FRAMEWORKS

How to build Context7 MCP Agent with another framework

ChatGPT Work logo

ChatGPT Work

Use Context7 MCP with ChatGPT Work

Antigravity logo

Antigravity

Use Context7 MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Context7 MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Context7 MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Context7 MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Context7 MCP with Claude Cowork

Codex logo

Codex

Use Context7 MCP with Codex

Kimi Code logo

Kimi Code

Use Context7 MCP with Kimi Code

Cursor logo

Cursor

Use Context7 MCP with Cursor

VS Code logo

VS Code

Use Context7 MCP with VS Code

OpenCode logo

OpenCode

Use Context7 MCP with OpenCode

OpenClaw logo

OpenClaw

Use Context7 MCP with OpenClaw

Hermes logo

Hermes

Use Context7 MCP with Hermes

CLI logo

CLI

Use Context7 MCP with CLI

Google ADK logo

Google ADK

Use Context7 MCP with Google ADK

LangChain logo

LangChain

Use Context7 MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Context7 MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Context7 MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Context7 MCP with LlamaIndex

CrewAI logo

CrewAI

Use Context7 MCP with CrewAI

FAQ

Frequently asked questions

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

Start with Context7 MCP.It takes 30 seconds.

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

Start building