METAGROK
BUILD / list-plugins-with-grok-cli

Build

List plugins with the Grok CLI

list-plugins-with-grok-cli

See which plugins Grok Build has installed or discovered for this environment before you enable, disable, or uninstall one, so you are not guessing from folder names alone. Official CLI Reference lists grok plugin <list|install|uninstall|update|enable|disable|details|validate> as the management surface, and Skills, Plugins & Marketplaces describes where plugins load from (./.grok/plugins/, ~/.grok/plugins/, marketplace installs, [plugins] paths, and --plugin-dir). Install the CLI from the Grok Build overview if it is not already on your PATH.

What you need

The Grok Build CLI signed in (grok login), a project directory (plugins can be project-local or user-global), and optional marketplace sources already configured under ~/.grok/config.toml. Neighboring jobs include Use skills and plugins in Grok Build for how skills and plugins compose, Open the Marketplace tab in Grok Build when you want to browse installable packs in the TUI, and Inspect what Grok Build loads when you need rules, hooks, and MCP origins in one dump. More Build jobs live on the Build hub.

List from the shell

  1. Confirm the CLI responds in the directory you care about:
cd /path/to/your-project
grok version
  1. Print the plugin list for this environment:
grok plugin list
  1. Cross-check discovery with inspect when a name is missing or you need to see how plugins merged with skills, hooks, and MCP servers:
grok inspect
# or
grok inspect --json
  1. Open the Plugins tab in the TUI when you prefer a modal over the shell. Inside an interactive grok session, run /plugins (documented under Modes and Commands); /hooks, /skills, /marketplace, and /mcps open the same extensions modal on other tabs.

Pitfalls

Listing from the wrong working directory hides project plugins under ./.grok/plugins/ that never appear in a bare home-directory check. Expecting grok plugin list alone to prove a marketplace source is configured fails when the pack never installed — open /marketplace or check [[marketplace.sources]] / known_marketplaces.json. Claude Code plugins that Grok auto-reads can show up through compatibility without a Grok-native install; use grok inspect when the origin is unclear.