Golden FrijolesSign in

Point Claude at a real project

This is a working connector for our demo shop. Paste it into Claude and ask it about the funnel, the North Star, or which features are on — it will answer from live data.

This is the demo project, not yours. The token below reads golden-beans-demo and nothing else. Your own project's URL lives inside the product, at Setup › Connect.Sign in for yours

Plan and build with an agent

Paste this into Claude Code, Codex, or any agent npx skills supports. It installs the Golden Frijoles plugin and starts you planning your first idea — the demo connector and CLI below are a different thing: your product's own data, once you have one connected.

Paste this into your agent
Install the golden-frijoles plugin. If you're in Claude Code, run `claude plugin marketplace add golden-frijoles/skills`, then `claude plugin install golden-frijoles@golden-frijoles`. If you're in another agent, run `npx skills add golden-frijoles/skills --skill '*'` and select your agent. Use one installation method. You can read the skill directly at https://github.com/golden-frijoles/skills/blob/main/plugins/golden-frijoles/skills/golden-frijoles/SKILL.md (raw: https://raw.githubusercontent.com/golden-frijoles/skills/main/plugins/golden-frijoles/skills/golden-frijoles/SKILL.md). Then use the golden-frijoles skill when working on this project, and start with its setup.

Demo connector URL

https://goldenfrijoles.com/api/v1/public/mcp/c/gb_connector_63207fc2c64941de8a9ad3838bc0c9933d9e4e60

Read-only. It serves one small shop's numbers and cannot change anything.

This URL is read-only on its own — it is displayed on this public page, so it can never authorize a change. To let your agent claim and resolve tasks, mint an agent write key in your dashboard and send it as a bearer token alongside this URL. Both must belong to the same project, and every change is previewed and confirmed before it applies.

Three steps

  1. Copy the URL above.
  2. Open Claude's connector settings.Add to Claude
  3. Paste it in and save. Then ask: what moved the North Star this week?

Or drive it from a terminal

The connector above is how an agent reads your project. The CLI is how it changes one — create a flag in every environment, roll it out, kill it. No browser, no human click.

npx @golden-frijoles/cli init

# then, the whole kill-switch story:
gf flags create checkout.demo_enabled --kill-switch --all-envs
gf flags rollout checkout.demo_enabled --env production --percent 25
gf flags kill checkout.demo_enabled --env production

npm i -g @golden-frijoles/cli puts gf on your PATH. Every command takes --json. Mint a token at Setup › CLI access once you have signed in.

For your engineers

An npm-installed SDK — a few lines to your first North Star input. It is the data-in layer under the connector above, not an alternative to it or to the CLI.

npm install @golden-frijoles/sdk

import { createGrowthEngineClient } from '@golden-frijoles/sdk'

const engine = createGrowthEngineClient({
  baseUrl: 'https://goldenfrijoles.com',
  apiKey: process.env.GROWTH_ENGINE_API_KEY,
  userId: currentUser.id,
})

await engine.track('setup_guide_viewed', { featureId: 'setup_guide' })
await engine.trackAdoption('setup_guide')
const variant = engine.bucket('quick-upload-ui', ['control', 'treatment'])

The same three steps, the same words and the same button as Setup › Connect inside the product. One flow, learned once — the only difference is whose numbers are on the other end, and this page says which in the first line.