Point Claude at a real project
This is a working connector for Golden Frijoles itself, the product built in the open with the product. Paste it into Claude and ask it about our funnel, our North Star, or which features are on — it will answer from live data.
Plan and build with an agent
Paste this into Claude Code, Codex, or any agent npx skills supports. Your agent reads install.md first, tells you what it installs, changes and contacts, and waits for your go-ahead. Then it runs claude plugin marketplace add golden-frijoles/skills and claude plugin install golden-frijoles@golden-frijoles (Claude Code) or npx skills add golden-frijoles/skills --skill '*' (other agents). The demo connector and CLI below are a different thing: your product's own data, once you have one connected.
Set up Golden Frijoles in this project. 1. Read https://goldenfrijoles.com/install.md before installing anything. 2. Tell me in a few lines what it installs, what changes on this machine and which services it contacts. Offer me a security review, and wait for my go-ahead. 3. Install it the way install.md says for the agent you are. 4. Run the setup skill from the golden-frijoles plugin.
Demo connector URL
https://goldenfrijoles.com/api/v1/public/mcp/c/gb_connector_63207fc2c64941de8a9ad3838bc0c9933d9e4e60Read-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
- Copy the URL above.
- Open Claude's connector settings.Add to Claude
- 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: frijoles flags create checkout.demo_enabled --kill-switch --all-envs frijoles flags rollout checkout.demo_enabled --env production --percent 25 frijoles flags kill checkout.demo_enabled --env production
npm i -g @golden-frijoles/cli puts frijoles 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({ apiKey: process.env.GROWTH_ENGINE_API_KEY })
engine.identify(currentUser.id) // after sign-in; events before it have no user
await engine.track('setup_guide_viewed', { featureId: 'setup_guide' })
await engine.trackAdoption('setup_guide')
const variant = engine.bucket('quick-upload-ui', [{ key: 'control' }, { key: 'treatment' }])
// a North Star input you push yourself, one value per day (re-pushing a day is a no-op)
const today = new Date().toISOString().slice(0, 10) // the UTC day the value belongs to
await engine.pushInputValues('attributed_revenue', [{ occurredOn: today, value: 1240 }])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.