Skip to Content
Home

Glubean

Docs: https://docs.glubean.com  · GitHub: https://github.com/glubean  · Landing: https://glubean.com 

Glubean is a workflow verification platform — the layer between intent and implementation. Write tests in TypeScript, commit to git, run locally or in CI. Supports HTTP, GraphQL, gRPC, and browser automation through plugins.

Two ways to use it:

  1. Test existing APIs — point the agent at your API, it writes tests that run, break, get repaired, and graduate to CI.
  2. Contract-first — describe what the API should do before it exists. The agent writes executable contracts (contracts/) that the future implementation must satisfy. After you build the API, the same contracts become your regression tests.

Core components

ComponentWhat it doesGet started
SDK (@glubean/sdk)Author tests — test(), configure(), assertions, builder flows, data-driven patterns. Tests are plain TypeScript, no proprietary format.SDK overview →
CLI (@glubean/cli)Run tests, emit traces, manage environments, initialize projects. Same runner in local dev and CI.CLI reference →
MCP server (@glubean/mcp)Lets AI agents run tests, read structured results, and self-repair — the bridge between agent and runner.MCP setup →
Skill (glubean/skill)Teaches AI agents SDK patterns, project conventions, and migration workflows. Agents write better tests with it.Skill setup →

These four are the foundation. Everything below builds on them.

Surfaces

VS Code Extension

The extension serves two roles:

  1. Postman replacement — explore/ is your API collection in code. Click the gutter play button to send a request, see full response (status, headers, body, timing) in the result viewer. Save parameter sets with test.pick, share via git. No Postman account, no per-seat pricing, no tool fragmentation.
  2. Visual layer for test results — run tests from gutter or Test Explorer, inspect structured traces (HTTP events, metrics, logs, step-by-step state), debug failures with typed expected vs actual.

The same TypeScript file works as both an API collection entry (explore/) and a CI regression test (tests/). No export step, no format conversion.

Cloud

Upload runs for team dashboards, analytics, alerts, and scheduled verification. Cloud is optional — the local workflow is fully functional without it.

Plugins

PluginProtocolPackage
GraphQLGraphQL queries and mutations@glubean/graphql
BrowserPuppeteer-based browser automation@glubean/browser
AuthToken management and refresh strategies@glubean/auth
gRPCgRPC client with proto loading@glubean/grpc (coming soon)

Start here

npx glubean config mcp        # MCP server — lets AI run and inspect tests
npx skills add glubean/skill   # Skill — teaches AI the SDK patterns

Then in your AI tool (Claude Code, Cursor, Codex):

"create a smoke test for the users API"

The agent writes the test, runs it via MCP, reads structured failures, fixes, and reruns — all in one conversation. See the full AI workflow →

By hand

npx @glubean/cli init
  1. Extension Quick Start — install and create a project
  2. Run Your First Test — write and run a test manually
  3. Connect CI
  4. Upload to Cloud

How it works

prompt → draft → inspect → repair → keep → CI → cloud
                                      ↑
                          (or write manually here)
  • Prompt: Describe what to verify. The agent uses your skill and project context.
  • Draft: Agent generates a TypeScript workflow with named steps, typed assertions, and shared state.
  • Inspect: Run in the extension. Structured traces show exactly which step failed and why.
  • Repair: Agent reads typed failures (expected vs actual), fixes, and reruns.
  • Keep: The same file moves from explore/ to tests/ — zero migration, same runner.
  • CI: glubean run tests/ in any CI pipeline.
  • Cloud: Upload runs for team dashboards, analytics, and alerts.

Choose a path

I want to…Start here
Generate and run tests with AIGenerate with AI
Write tests myselfSDK overview → Test shape → Assertions
Explore APIs in my editorExtension → Running tests
Get team visibilityCloud → Upload first run
Migrate from Postman / OpenAPI / legacy testsMigration guide
Define API contracts before implementationContract-first

Why teams adopt Glubean

  • explore/ replaces Postman — your API collection lives in git, not a proprietary cloud. No per-seat pricing.
  • Agent output is not throwaway — the same file graduates from explore/ to CI without rewriting
  • Structured failures — AI and humans read typed expected vs actual, not terminal noise
  • One codebase across local development, CI, and production verification
  • Git-safe — TypeScript files, no binary formats, no merge conflicts
  • No vendor lock-in — tests are plain TypeScript. If Glubean disappears, your code still runs.

From the blog

Last updated on
Overview