Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Schema
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_time | IMPORTANT: This tool should be automatically called when users ask "지금 몇시", "현재 시간", "몇시야", "what time", "current time", "time now", "what's the time" or similar questions. Get current time |
| create_thinking_chain | IMPORTANT: This tool should be automatically called when users say "생각 과정", "사고 흐름", "연쇄적으로", "thinking process", "chain of thought", "reasoning chain" or similar keywords. Create sequential thinking chain |
| analyze_problem | IMPORTANT: This tool should be automatically called when users say "문제 분석", "어떻게 접근", "분석해줘", "analyze this", "how to approach", "break this down" or similar keywords. Break down complex problem into structured steps |
| step_by_step_analysis | IMPORTANT: This tool should be automatically called when users say "단계별", "차근차근", "하나씩", "step by step", "one by one", "gradually" or similar keywords. Perform detailed step-by-step analysis |
| break_down_problem | IMPORTANT: This tool should be automatically called when users say "나눠서", "단계별로", "세분화", "break down", "divide", "split into parts" or similar keywords. Break complex problems into sub-problems |
| think_aloud_process | IMPORTANT: This tool should be automatically called when users say "생각해봐", "고민해봐", "어떻게 생각해", "think about it", "let me think", "reasoning" or similar keywords. Generate think-aloud reasoning process |
| format_as_plan | IMPORTANT: This tool should be automatically called when users say "계획으로", "정리해줘", "체크리스트", "format as plan", "make a plan", "organize this", "checklist" or similar keywords. Format content into clear plans |
| monitor_console_logs | IMPORTANT: This tool should be automatically called when users say "콘솔 로그", "에러 확인", "로그 봐줘", "console", "check logs", "debug output", "console errors" or similar keywords. Monitor browser console |
| inspect_network_requests | IMPORTANT: This tool should be automatically called when users say "네트워크", "API 호출", "요청 확인", "network", "API calls", "check requests", "network traffic" or similar keywords. Inspect network requests |
| save_memory | IMPORTANT: This tool should be automatically called when users say "기억해", "remember", "저장해", "save this", "keep this", "memorize" or similar keywords. Save information to long-term memory |
| recall_memory | IMPORTANT: This tool should be automatically called when users say "떠올려", "기억나", "recall", "remember what", "what was", "remind me" or similar keywords. Retrieve information from memory |
| list_memories | IMPORTANT: This tool should be automatically called when users say "뭐 있었지", "저장된 거", "목록", "what did I save", "list memories", "show saved" or ask about stored items. List all stored memories |
| delete_memory | IMPORTANT: This tool should be automatically called when users say "잊어", "삭제해", "지워", "forget this", "delete memory", "remove", "erase" or similar keywords. Delete specific memory |
| search_memories | IMPORTANT: This tool should be automatically called when users say "찾아", "검색", "기억 중에", "search memory", "find in memories", "look for" or similar keywords. Search memories by content |
| update_memory | IMPORTANT: This tool should be automatically called when users say "수정해", "업데이트", "바꿔", "update memory", "change", "modify", "edit memory" or similar keywords. Update existing memory |
| auto_save_context | IMPORTANT: This tool should be automatically called when users say "커밋", "commit", "저장", "save", "checkpoint", "backup" or similar keywords. Automatically save current context |
| restore_session_context | IMPORTANT: This tool should be automatically called when users say "복원", "이전 상태", "되돌려", "restore", "go back", "previous state", "revert" or similar keywords. Restore previous session context |
| prioritize_memory | IMPORTANT: This tool should be automatically called when users say "중요한 거", "우선순위", "prioritize", "important ones", "what matters", "priority" or similar keywords. Prioritize memories by importance |
| start_session | IMPORTANT: This tool should be automatically called when users greet with "하이아이", "hi-ai", "안녕", "hello", or similar greetings. It loads project context, previous memories, and restores the last session state to continue work seamlessly. |
| get_coding_guide | IMPORTANT: This tool should be automatically called when users say "가이드", "규칙", "컨벤션", "guide", "rules", "convention", "standards", "best practices" or similar keywords. Get coding guide |
| apply_quality_rules | IMPORTANT: This tool should be automatically called when users say "규칙 적용", "표준 적용", "apply rules", "apply standards", "follow conventions", "적용해" or similar keywords. Apply quality rules |
| validate_code_quality | IMPORTANT: This tool should be automatically called when users say "품질", "리뷰", "검사", "quality", "review code", "check quality", "validate", "코드 리뷰" or similar keywords. Validate code quality |
| analyze_complexity | IMPORTANT: This tool should be automatically called when users mention "복잡도", "복잡한지", "complexity", "how complex", "is it complex", "difficulty level" or similar keywords. Analyze code complexity |
| check_coupling_cohesion | IMPORTANT: This tool should be automatically called when users say "결합도", "응집도", "coupling", "cohesion", "dependencies check", "module structure" or similar keywords. Check coupling and cohesion |
| suggest_improvements | IMPORTANT: This tool should be automatically called when users say "개선", "더 좋게", "리팩토링", "improve", "make better", "refactor", "optimize", "enhance code" or similar keywords. Suggest improvements |
| generate_prd | IMPORTANT: This tool should be automatically called when users mention "PRD", "요구사항 문서", "제품 요구사항", "product requirements", "requirements document", "spec document" or similar terms. Generate Product Requirements Document |
| create_user_stories | IMPORTANT: This tool should be automatically called when users mention "스토리", "사용자 스토리", "user story", "user stories", "as a user" or similar terms. Generate user stories from requirements |
| analyze_requirements | IMPORTANT: This tool should be automatically called when users say "요구사항 분석", "필요한 것들", "requirements analysis", "what we need", "analyze requirements", "필수 기능" or similar keywords. Analyze project requirements |
| feature_roadmap | IMPORTANT: This tool should be automatically called when users say "로드맵", "일정", "계획표", "roadmap", "timeline", "project plan", "development schedule" or similar keywords. Generate development roadmap |
| enhance_prompt | IMPORTANT: This tool should be automatically called when requests are vague, too short (under 20 chars), or when users say "구체적으로", "자세히", "명확하게", "더 구체적으로", "be specific", "more detail", "clarify", "elaborate" or similar keywords. Transform vague requests |
| analyze_prompt | IMPORTANT: This tool should be automatically called when users ask "프롬프트 분석", "평가", "점수", "얼마나 좋은지", "analyze prompt", "rate this", "score", "how good", "prompt quality" or similar keywords. Analyze prompt quality |