AgileBuilder logoAgileBuilder
Back to docs

Introduction

What AgileBuilder is — an open-source Git-template scaffolding CLI with cloud spaces and MCP integration, so AI and your team start every project from the same standard

What is AgileBuilder

AgileBuilder is a Git-template-based project scaffolding and developer-resource management tool, made up of two parts:

  • Open-source CLI (MIT license): installed globally via npm, providing the agilebuilder / ag commands. It generates project skeletons from a Git template URL or a registered template resource, with support for template variables (EJS rendering), file-path rendering, and post-generation Hooks. A built-in agilebuilder-mcp server mode lets AI tools call into it.
  • AgileBuilder Cloud: SSO accounts, personal/team spaces, cloud resource management, and subscription billing — so templates and standards documents sync across devices and can be shared within a team.

AgileBuilder itself never calls any LLM. Its job is to distill your project structure and team standards into templates and documents; AI tools read those assets over the MCP protocol and work inside your conventions.

What problems it solves

With AI-assisted coding now the norm, project creation exposes two recurring problems:

  • AI doesn't follow your conventions: asking AI to scaffold a project directly produces a different directory layout, dependency set, and toolchain configuration every time. Team standards sit unread in a wiki — and invisible to the AI.
  • Inconsistent project starting points: every team member copies an old project and hand-edits configs; projects drift apart and review/maintenance costs climb.

AgileBuilder's answer: codify proven project structures and standards as templates, so both humans and AI start from the same template.

The core guarantee: same template + same parameters = same project skeleton — reproducible and auditable.

Three core ideas

Constrain the AI

The CLI ships with a built-in MCP server (agilebuilder-mcp). MCP-capable AI tools such as Cursor, Claude Code, and Codex can query your template library and standards documents, and generate project skeletons from your templates — instead of improvising from a prompt.

Templates as assets

A template is just a Git repository plus a .agilebuilder.config.yaml file. Templates are versioned, reviewable, and evolve with your team; variables and Hooks let one engineering pattern adapt to many projects.

Open source and free to start

The CLI is MIT-licensed open source. All local features are free forever, work offline, and require no account. Subscribe to cloud spaces only when you need sync and team collaboration.

How the CLI and the cloud relate

Open-source CLI (local)AgileBuilder Cloud
CostFree (MIT)Free tier is read-only; Pro/Trial can write; annual subscription
AccountNot requiredSSO sign-in (email code / WeChat / GitHub / Google)
Data storageLocal ~/.agilebuilder/v2Cloud spaces + local cache
Resource scopeLocal templates and docsPersonal spaces, team-shared resources
CollaborationSingle userMembers, roles, permissions

Both forms share one CLI: without signing in you work in the built-in local workspace; after ag login you can access cloud spaces, and the workflow is identical across local and cloud.

Who it's for

  • Individual developers: codify your go-to project structures and init flows as templates — maintain once, reuse forever, fully offline and free.
  • Tech leads / engineering teams: unify the team's project starting point and feed standards documents to AI via MCP, cutting review and rework costs.
  • Template authors: maintain templates as Git repositories and optionally publish them to the Resource Plaza for your team and the community.

Next steps