Grok Just Launched Plugins. Here Are the 10 Best Grok Plugins

Grok Build's plugin system landed in 2026 and the official marketplace at github.com/xai-org/plugin-marketplace has been filling out fast. xAI ships a curated set (Vercel, Sentry, Chrome DevTools, Cloudflare, MongoDB, Neon, Superpowers, Firecrawl), and a wider community has been publishing skill packs and MCP servers that drop into the same install flow.

The reason plugins matter more than any single Grok feature this year is reach. One install can ship a workflow, an app connector, and an MCP server together. You stop pasting setup instructions into project docs and start sharing a single command from the marketplace. The right combination of plugins turns Grok from a capable agent into one that knows your APIs, your deploys, your tickets, and the live web.

These are the ten best Grok plugins I'd hand someone setting up a fresh Grok Build session today.

A Grok plugin is a directory that bundles any combination of these components into a single install:

• Skills (skills/): SKILL.md files that teach Grok how to handle a task. The format is shared across coding agents, which is why a lot of the most-installed agent skills work in Grok Build with no modification
• Commands (commands/): slash commands
• Agents (agents/): subagent definitions
• Hooks (hooks/hooks.json): lifecycle hooks
• MCP servers (.mcp.json): live tool surfaces over MCP
• LSP servers (.lsp.json): language server configs

One plugin can ship all of these. The Firecrawl plugin, for example, registers the hosted Firecrawl MCP server alongside skills that teach Grok when to reach for search, scrape, crawl, map, or interact. The full spec lives in the plugin marketplace repo, and the catalog itself sits in .grok-plugin/marketplace.json.

Running /plugin inside Grok Build opens the marketplace directly in the CLI.

The marketplace is browsable inside Grok Build via the /plugin slash command. The same directory ships in the Grok Build desktop app and CLI.

1. Open the marketplace. Type /plugin inside any Grok Build session. You get the catalog, searchable by name and keyword.

2. Install. Pick a plugin and Grok Build clones it from the pinned commit SHA, registers its skills, commands, MCP tools, and hooks, and prompts for any required credentials on first use.

3. Invoke it. Most plugins activate implicitly when your prompt matches a skill's trigger. You can also call a plugin explicitly with @plugin-name or run its slash commands.

4. Manage it. Plugins can be disabled, updated, or removed from the same /plugin panel.

The marketplace pins every third-party plugin to a full commit SHA so a vendor force-push can't silently change what gets installed. xAI's README is also explicit that third-party plugins are provided as-is and at your own risk.

Not everything in this list is a first-party Grok plugin. A few are official entries in the xAI marketplace. The rest are a mix: MCP servers, skill collections, and plugin-style tools that fit naturally into a Grok Build workflow even though they live outside the curated catalog. Inside a real session, you stop noticing the difference, which is exactly how it should feel.

An agent is only as smart as the context it has. The Firecrawl plugin gives Grok live web context.

Grok's built-in web tools have a place for quick lookups, but they aren't built for full-page extraction, recursive crawls, or live browser interaction. The Firecrawl plugin fills that gap. It bundles the hosted Firecrawl MCP server plus a set of skills, giving Grok the ability to search the web, scrape clean markdown from any URL, map a domain, crawl entire sites, and drive a live browser session on a scraped page.

The plugin works through MCP, so Grok can chain operations naturally: search to find sources, scrape to read them in full, crawl to index an entire documentation site, interact to click through pages that need logins or pagination. JavaScript rendering, anti-bot handling, and proxy rotation are all automatic. Results write to a local .firecrawl/ directory when output is large, so Grok's context window stays clean.

The bundled MCP is keyless on eligible networks (1,000 free credits per month, no signup), and the first action you take signs you in through your browser if you want a key for higher limits. No API key paste required.

Install:

In Grok Build, run /plugin and search for firecrawl, then select it to install. This installs the skills and the hosted Firecrawl MCP in one step.

/plugin
# search "firecrawl" and install

Example:

"Check the Next.js 16 migration guide and list every breaking change for App Router"
"Crawl the Stripe API docs and find every endpoint that supports idempotency keys"
"Research our top three competitors and extract their pricing pages as structured JSON"

Honest take: Live results replace anything cached for documentation lookups, research, and competitor analysis. File-based output keeps context efficient on big crawls. Used by 1.25M+ developers and 150,000+ companies, with 5B+ requests served. When xAI announced the plugin, the response was immediate:

Cons: Heavy usage consumes credits past the free tier, and very large crawls benefit from a paid plan. If you are comparing options across agents, the best web search MCP servers guide covers how Firecrawl stacks up against Tavily and Exa.

Full reference at github.com/firecrawl/firecrawl-grok-plugin.

The most-used third-party skill collection for AI coding agents, and it drops cleanly into Grok Build.

143k GitHub stars (as of June 2026)

Matt Pocock's skill repo started as a Claude Code companion and has grown into the most-installed engineering skill pack across every major coding agent. The pitch on the repo: skills built to fix the four recurring failure modes of AI coding agents, namely misalignment, verbosity, broken code, and ball-of-mud architecture. Each skill targets one of those directly.

The headliners: grill-me interviews you about every decision in a plan until you reach shared understanding before any code is written. handoff compresses a session into a markdown document so you can continue in a fresh worktree or hand off to a different agent. tdd runs a strict test-first loop. diagnose stress-tests a hypothesis before committing to a fix. caveman strips response verbosity to the bone (covered separately below).

Install:

npx skills@latest add mattpocock/skills

Then run /setup-matt-pocock-skills inside Grok Build to configure your issue tracker (GitHub, Linear, or local), triage labels, and documentation locations.

Example:

"Grill me on the auth refactor plan before I touch any code"
"Run handoff so I can continue this in a new Grok worktree"
"Use the tdd skill to add validation to the signup endpoint"

Honest take: The whole collection is built around a strong opinion about how to ship code with an agent, drawn from Pragmatic Programmer, DDD, and Ousterhout's A Philosophy of Software Design. The same SKILL.md files work across Grok Build, Claude Code, Codex, Cursor, and Gemini CLI, so there's nothing Grok-specific to learn.

Cons: Some skills (especially grill-me) are deliberately slow by design. They surface assumptions you would otherwise skip past, which means the agent moves more carefully. That is the point, but it adds friction on small tasks.

Full reference at github.com/mattpocock/skills and the deeper guide at aihero.dev.

Composio connects Grok to 1,000+ SaaS apps with managed OAuth in a single tool surface.

The reason Composio matters for Grok is the auth tax. Connecting an agent to Gmail, HubSpot, Salesforce, Notion, Linear, Stripe, or Slack means handling OAuth flows, refresh tokens, scopes, and rate limits for every service separately. Composio handles all of that as a hosted service: you authorize once per app, Grok gets a unified tool surface, and per-user credentials are managed for you. Composio is SOC2 and ISO 27001:2022 certified, with customers including Zoom, Letta, Glean, and HubSpot.

The integration pattern stays the same regardless of the app. Grok sees a tool like gmail_send or hubspot_create_contact, calls it, and Composio routes the request through the right OAuth session. Sandboxed execution and parallel calls across apps work out of the box.

Install:

Composio ships as an MCP server. Add it to Grok Build's MCP config:

npx composio-mcp@latest init

Then sign in at composio.dev and authorize the apps you want Grok to act on.

Example:

"Pull the last 10 unanswered emails from my inbox and draft replies"
"Create a HubSpot deal for every Stripe invoice over $5,000 in the last week"
"Find the Notion page about Q3 planning and add today's standup notes"

Honest take: One install, hundreds of integrations. Managed OAuth means you stop building one-off connectors. Per-user credentials work cleanly for multi-tenant agent products. If you are building an agent that needs to act on third-party services rather than answer questions about them, Composio collapses weeks of integration work, and it shows up consistently on every roundup of the best MCP servers for developers.

Cons: Hosted service, so you depend on Composio's uptime and rate limits. The free tier is enough for development but production usage moves to paid plans. Some niche apps still expose only a subset of their full API through Composio.

Full reference at composio.dev.

Obra's Superpowers is a cross-harness agent workflow framework with first-class Grok Build support, and it's now an official entry in the xAI marketplace.

237k GitHub stars (as of June 2026)

Superpowers is the most-starred agent workflow framework on GitHub. It started in the Claude Code ecosystem, picked up Codex support, and now ships as an official Grok plugin in the xAI marketplace under the development category. The framework bundles a curated skill collection, subagent dispatch patterns (spawn_agent, wait_agent), code-review loops, and worktree management primitives.

If Matt Pocock's skills are about engineering judgment, Superpowers is about agent orchestration. It is the layer that turns Grok from one agent doing one thing into a coordinated set of subagents handling planning, implementation, review, and verification in parallel, which is the same Codex multi-agent orchestration pattern you'd recognize from the OpenAI side.

Install:

Install through the marketplace:

/plugin
# search "superpowers" and install

Or via the npx skills flow if you want the upstream version directly:

npx skills add https://github.com/obra/superpowers

Example: