TrialStack Catalyst and Grok Bot

Grok Bot runs persistent agents on a cloud computer. Grok Build is the separate terminal coding agent; its installation commands do not install a connector in Grok Bot.

Availability

The TrialStack Catalyst repository includes a Cursor-format plugin candidate for Grok Bot, alongside Codex and Grok Build manifests. All use the same Catalyst MCP endpoint and governed skill.

The candidate has not been published in Grok Bot’s Marketplace. Native installation, TrialStack sign-in, and the first tool request have not been verified. The public repository alone does not make the connector available in Grok Bot.

Connect when the plugin is available

Grok Bot’s official connector guide describes this process:

1. Open Marketplace in the sidebar and find the plugin.
2. Choose Add and complete browser authentication when prompted.
3. Attach the connector to a task using @.

If TrialStack Catalyst is not listed, this installation path is not available yet. Do not substitute the Grok Build terminal commands or Cursor’s local plugin folder for native Grok Bot installation.

Verify the connection

Once installation and sign-in are available, ask:

Use TrialStack Catalyst to list the organizations I can access. Do not make changes.

Choose a returned organization, then request its trials. Your existing TrialStack permissions still apply. An empty trial list can be a valid result.

For changes, request a preview first and approve it in a separate message only after reviewing it. See Model Context Protocol (MCP) for the governed workflow.