xAI Ships Grok Build Plugin Marketplace With MongoDB, Vercel, Sentry, Chrome DevTools, Cloudflare, and Superpowers Plugins at Launch

Today, xAI shipped the Grok Build Plugin Marketplace. It is a built-in catalog of plugins for Grok Build, the company’s terminal coding agent. A plugin bundles skills, slash commands, agents, hooks, MCP servers, and LSPs into one package. You browse, install, and update these packages without leaving the terminal.

Grok Build is xAI’s coding agent and CLI for software engineering work. The marketplace adds a discovery and distribution layer on top. Before this, developers wired up each integration one at a time. Now a single command pulls a complete bundle into the agent. The catalog lives in the open repo xai-org/plugin-marketplace on GitHub. That repo is an index. It points at plugin sources so Grok Build can fetch them.

A plugin is a directory bundling any combination of six component types. Each type maps to a specific file or folder. The table below lists them.

An optional plugin.json manifest adds metadata or overrides component paths. So one install can extend the agent in several ways at once.

Inside Grok Build, type /marketplace to browse the catalog. Press i to install a selected plugin. You can also run commands directly from the shell:

The install command carries a --trust flag. That matters because plugins can execute code and access data on your system.

The marketplace opens with six plugins from partners across the stack. Each targets a concrete workflow.

Example: a data scientist hits a slow MongoDB query. They install the MongoDB plugin, then ask the agent to optimize it. Example: a frontend engineer installs Chrome DevTools to inspect network requests during a failing render. Example: an on-call engineer installs Sentry to triage a stack trace from production.

Every remote plugin pins a full 40-character lowercase commit SHA. Grok Build re-verifies git rev-parse HEAD == sha after cloning. Without a pin, a force-push or repo compromise could ship new code silently. The pin closes that path at install time. The repo also separates first-party plugins, maintained by xAI, from third-party ones. xAI states it does not author, control, or verify third-party plugins. They ship AS-IS, and you install at your own risk.

The catalog is open to contributions. To add a plugin, edit .grok-plugin/marketplace.json and open a pull request. A remote entry looks like this:

A generated plugin-index.json records each plugin’s components. You never hand-edit that file. Regenerate it with python3 scripts/generate-plugin-index.py . CI runs the same script with --check and fails on stale files.