AI Agent — Claude Code, Claude Desktop, Cursor, 또는 MCP 호환 호스트가 제공하는 모델 Context Protocol (MCP) 서버는 JDL (JHipster Domain Language)를 사용하여 비계 및 진화 애플리케이션에 JHipster CLI를 구동합니다.

당신은 응용 프로그램을 설명하거나 당신이 원하는 변경; 에이전트는 JDL로 변환, 그것을 검증, 및 실행 JHipster - 이 서버는 모든 실행을 유지 ** 비-interactive, 디렉토리에 sandboxed 당신은 이름, 그리고 그것을 쓰기 전에 안전한**.

문서

** 전체 사용자 가이드 → docs/.** 당신이 JHipster를 알고 있지만 MCP에 새로운 경우, 거기 시작 하 고 순서에 읽으십시오:

1. 소개 - MCP 서버가 무엇인지, 도구 / 리소스 / 프롬프트 모델.
2. 설치 - 호스트에 연결.
3. 시작하기 - 첫 번째 가이드 세션.
4. 도구 참조 · 5. 자원 · 6. Prompts
5. 서버가 컨텍스트를 관리하는 방법
6. 진보된 사용법 & 주문화
7. 어떻게 작동 (엔진)

로드맵: docs/ROADMAP.md.

빠른 시작

** 필수품:** Node.js 20+ 및 작업 글로벌 jhipster CLI on your PATH] ([T3]]). 서버는 기존의 jhipster 바이너리를 파괴한다 - 발전기를 묶지 않습니다. 임명에 있는 가득 차있는 세부사항.

jhipster-mcp

A Model Context Protocol (MCP) server that lets AI agents — Claude Code, Claude Desktop, Cursor, or any MCP-compatible host — drive the JHipster CLI to scaffold and evolve applications using JDL (JHipster Domain Language).

You describe the app or change you want; the agent translates it to JDL, validates it, and runs JHipster — while this server keeps every run non-interactive, sandboxed to a directory you name, and safe to preview before it writes.

📖 Documentation

Full user guide → docs/. If you know JHipster but are new to MCP, start there and read in order:

1. Introduction — what an MCP server is, and the tools / resources / prompts model.
2. Installation — connect it to your host.
3. Getting started — your first guided session.
4. Tools reference · 5. Resources · 6. Prompts
5. How the server manages context
6. Advanced usage & customization
7. How it works (engine)

Roadmap: docs/ROADMAP.md.

Quick start

Prerequisites: Node.js 20+ and a working global jhipster CLI on your PATH (npm install -g generator-jhipster). The server spawns your existing jhipster binary — it does not bundle the generator. Full details in Installation.

Claude Code

claude mcp add jhipster -- npx -y jhipster-mcp

Claude Desktop / Cursor / other hosts

Add this to your host’s MCP config (e.g. claude_desktop_config.json), then restart:

{
  "mcpServers": {
    "jhipster": {
      "command": "npx",
      "args": ["-y", "jhipster-mcp"]
    }
  }
}

Then ask your host something like “Create a JHipster monolith in /tmp/demo with a Product entity.” See Getting started for a full walkthrough and more examples.

What’s inside (at a glance)

• 13 tools — validate_jdl, create_app_from_jdl, import_jdl, add_entity, add_relationship, set_option, info, project_commands, upgrade_advisor, preview_upgrade, generate_ci_cd, generate_deployment, run_jhipster. (reference)
• Resources — the JDL grammar plus live project state (yo-rc, entities, exported jdl). (reference)
• Prompts — scaffold_crud_monolith, add_audit_fields, monolith_to_microservices. (reference)
• Safe by design — directory scoping, empty-dir guard, no shell, JDL-injection guards, and isolated preview/dryRun. (details)

Development

npm run dev         # tsup --watch
npm run typecheck   # tsc --noEmit
npm run build       # tsup → dist/index.js