gx — Claude Code plugin

The gx plugin connects Claude Code to a gx workspace so you can capture product thinking — observations, half-formed ideas, customer feedback, decisions — directly into a structured knowledge graph.

Once installed:

• The gx-capture skill walks you through Signal → Need → Work (or builds a full Initiative — experiment or campaign) and persists the nodes via gx's MCP server.
• The MCP server is auto-configured. First time you use it, your browser opens for OAuth; every session after that is silent.
• gx auto-completes "Install the plugin" on your setup checklist the first time it sees an authenticated call from you.

Install

/plugin marketplace add gxtools/gx-marketplace
/plugin install gx@gxtools

(Once published.)

Configure

On first install, Claude Code prompts for a gx_url. Use:

• https://gx.tools for the hosted product (default)
• http://localhost:3030 if you're running gx locally

You can change this later via Claude Code's plugin settings.

Develop locally

This directory is structured as a standalone plugin repo — you can git init it, push to a repo, and submit to the marketplace from here without modification.

To test the plugin against a local gx dev server:

1. Run gx locally (pnpm dev in the gx repo, listens on :3030).
2. Install the plugin from this local path:

   /plugin marketplace add ./plugin
   /plugin install gx
   

   When prompted for gx_url, enter http://localhost:3030.
3. Restart Claude Code. The skill should appear under /skills and the MCP tools should be reachable.

Layout

plugin/
├── .claude-plugin/
│   └── plugin.json           — manifest (name, version, userConfig)
├── .mcp.json                 — MCP server auto-config (HTTP, takes user's gx_url)
├── hooks/
│   └── hooks.json            — PluginInstalled webhook → /api/plugin/hello
├── skills/
│   └── gx-capture/
│       └── SKILL.md          — the capture skill prompt
├── PUBLISHING.md             — marketplace submission process
└── README.md                 — this file

How "auto-complete setup step 3" works

Two telemetry events fire when you install:

1. /api/plugin/hello (anonymous) — called by the PluginInstalled hook before OAuth has happened. Used for funnel analytics ("someone installed but didn't connect"). Logged server-side, no userId.
2. First authenticated MCP call (gx route handler) — when you make any gx tool call after authorizing OAuth, gx marks setup-checklist step 3 complete for your user (across all your projects' checklists, idempotent) and fires the plugin_hello_received PostHog event.

This split means you can install + abandon and we'll see the drop-off, and the in-app checklist is robust to anonymous-hook failures.