[dora-dotcom]

Why

Grok Build's plugin marketplace (xai-org/plugin-marketplace) is another place people can find and install box. Low effort, and it doesn't wait on the org owner.

What

• grok/: .grok-plugin/plugin.json, .mcp.json with https://mcp.box.simular.ai/mcp (http, OAuth sign-in through /mcps, no key in the package), the box skill, README and LICENSE. Same shape as TinyFish's and Browser Use's grok/ folders in the marketplace.
• README: a row in the table and a release step.

After merge

Open a PR to xai-org/plugin-marketplace adding box as a remote source pinned to the merge commit on main, path: grok (the entry is ready locally), and regenerate their plugin index.

Checks

• grok plugin validate ./grok (Grok 1.0.70): manifest valid, 1 skill dir, MCP servers.
• Installed from this branch the way the marketplace will (grok plugin install simular-ai/box-plugin@grok#grok); grok mcp doctor saw box and got "Auth required" before sign-in.
• Real run on Grok Build 1.0.70 (Grok 4.7): /mcps → box → i signed in through the browser. "take a screenshot of my box" read the skill, called one tool and described the live desktop; "open Hacker News in my box and summarize the top 5 posts" opened Chrome in the box (seen live on box.simular.ai/box) and summarized the posts.
• Privacy link points at the current Sai privacy page until the box-neutral one is up.

🤖 Generated with Claude Code

[dora-dotcom]

@chenchenSimular tested end to end on a real Grok Build 1.0.70 (sign-in, screenshot, Hacker News in the box's Chrome). Could you take a look when you have a minute? After merge I'll send the xai-org/plugin-marketplace PR pinned to the merge commit. thanks!

[chenchenSimular]

Looks good. The package matches xAI's plugin format (.grok-plugin/plugin.json + .mcp.json, same shape as TinyFish's entry), uses https://mcp.box.simular.ai/mcp with OAuth only, and has no secrets.

Please add CI here or in a quick follow-up. No checks ran on this PR because grok/** isn't in publish-cli.yml's pull_request.paths:

• Add grok/** to the path filter.
• In the plugins job, run grok plugin validate ./grok, with the Grok version pinned in cli/e2e/clients.json.

Non-blocking:

• For the xai-org marketplace entry, use brand keywords only (xAI's review rejects generic ones like computer-use / cloud-computer).
• README step 2 (/marketplace, find box) only works once the xai-org PR merges; worth a note.

[dora-dotcom]

@chenchenSimular thanks! Added both:

• CI: grok/** in the path filter, and a plugins step that installs Grok 1.0.70 (pinned in cli/e2e/clients.json) with xAI's installer and runs grok plugin validate ./grok. Checked the same step locally in a fresh HOME.
• README: until box is in xAI's marketplace, step 2 points at grok plugin install simular-ai/box-plugin#grok (tested, installs box).
  For the xai-org entry I'll keep keywords to brand names only.

[chenchenSimular]

@dora-dotcom this now conflicts with main in README.md (the client table). Could you rebase it? I'll take another look at the two commits added after my approval once it's rebased.

[dora-dotcom]

Merged main into the branch to fix the README conflict (kept both the OpenAI and Grok rows, and the grok/ release line next to the new CLI notes); a squash merge comes out the same as a rebase. No other changes. The two commits after your approval: the CI step (grok plugin validate) and the README line for installing from this repo until box is in xAI's marketplace.