SplitHub

Declare experiments in splithub.config.ts, render variants with React, and read a plain verdict from the CLI, the MCP server or the dashboard. Your coding agent can do all of it for you.

npx splithub init

Why SplitHub

• Config in your code. Experiments live in splithub.config.ts, reviewed in pull requests like everything else.

• No flicker, no network on render. Who sees which variant is a local hash, decided before the first paint.

• Made for agents. The CLI answers in JSON, and the MCP server gives Claude Code, Cursor and Codex the same tools you have.

• A verdict, not a dashboard to decode. SplitHub Cloud says when a variant wins, and peeking early never fools it.

• Your data, if you want it. Send events to your own database instead, and read the raw numbers per variant.

Related MCP server: RoadBoard

Three steps

1. Describe the test.

// splithub.config.ts
import { defineConfig } from '@splithub/core';

export default defineConfig({
  project: 'my-app',
  storage: { mode: 'cloud', key: 'pk_...' }, // or { mode: 'self', endpoint: '/api/splithub' }
  goals: { signup: { type: 'event' } },
  experiments: {
    'hero-title': {
      kind: 'value',
      status: 'running',
      variants: {
        control: { weight: 50, value: 'Ship faster' },
        direct: { weight: 50, value: 'Know which version wins' },
      },
      goal: 'signup',
    },
  },
});

2. Show the variant and count the goal.

import { SplitHubProvider, useValue, useTrack } from '@splithub/react';
import config from './splithub.config';

function Hero() {
  const title = useValue<string>('hero-title');
  const track = useTrack();
  return (
    <>
      <h1>{title}</h1>
      <button onClick={() => track('signup')}>Sign up</button>
    </>
  );
}

export const App = () => (
  <SplitHubProvider config={config}>
    <Hero />
  </SplitHubProvider>
);

3. Read the result.

npx splithub status              # every test with its verdict
npx splithub results hero-title  # lift, chance to beat control, confidence interval

Using Next.js? @splithub/next adds middleware and server components. No build step? One script tag from @splithub/browser runs redirect tests.

With your coding agent

claude mcp add splithub -- npx -y @splithub/mcp

Or let the CLI write .mcp.json for Claude Code and .cursor/mcp.json for Cursor:

npx splithub skills --mcp

Then ask in plain words: "test a shorter headline on the pricing page" or "is the new checkout winning?".

Packages

Two complete apps live in examples/: Vite + React and Next.js.

Cloud or your own database

Develop

pnpm install
pnpm build
pnpm test

Node 22.13 or newer, pnpm 10.

Contributing

Issues and pull requests are welcome. See CONTRIBUTING.md. Found a security problem? See SECURITY.md.

License

MIT