Agent Plugins Marketplace
← All plugins

grok

v0.2.14

Grok Build CLI에 코딩 작업을 위임하는 MCP 브리지 (route · nextAction · worktree · subscription-safe)

Claude Code2 Skills1 MCP serverstdio

By xzawed1 GitHub starsUpdated 15 hours ago

Directory evidence

Runtimes
Claude Code
Parsed components
3 skill or MCP entries
Source updated
Sep 2, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install grok for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install grok@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/xzawed/claude-grok-build-plugin

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.

Plugin files

grok/
├── .claude-plugin/plugin.json
├── skills/grok-first-mile/SKILL.md
├── skills/grok-routing/SKILL.md
└── .mcp.json

Included Skills2

grok-first-mileskills/grok-first-mile/SKILL.md

Onboarding and first-session guidance for the Grok Claude Code plugin. Use when the user is new to the plugin, asks how to use Grok, wants a tour, setup help, or what to try first — or when they just installed the plugin and need a clear starting path.

grok-routingskills/grok-routing/SKILL.md

When to delegate coding work to Grok Build vs handle it in Claude. Use whenever the user asks for bulk edits, test backfill, migrations, boilerplate, exploratory prototypes, or whether to use /grok:delegate — and when reviewing whether a task is safe to hand to Grok.

MCP servers1

grok-buildstdio
command
node
args
${CLAUDE_PLUGIN_ROOT}/mcp-server/dist/index.js

MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.

Plugin manifests1

.claude-plugin/plugin.json
{
  "name": "grok",
  "version": "0.2.14",
  "description": "Grok Build CLI에 코딩 작업을 위임하는 MCP 브리지 (route · nextAction · worktree · subscription-safe)",
  "author": {
    "name": "xzawed"
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[grok on Agent Plugins Marketplace](https://pluginsmp.com/plugins/grok)